cancel
Showing results for 
Search instead for 
Did you mean: 

unable to open integration repository , integration directory is opening .

Former Member
0 Kudos

hi We are having a problem when we try to open integration repository. the error that we are getting isgive below. But we are able to opent integration directory , can any body help in resolving this. \

An error occurred while launching/running the application.

Title: Integration Builder

Vendor: SAP AG

Category: Launch File Error

JAR resources in JNLP file are not signed by same certificate

thanks and regards

pendyala

Accepted Solutions (1)

Accepted Solutions (1)

JoelTrinidade
Active Contributor
0 Kudos

Hi Pendyala,

You can go through

Go thru this blog Unable to open Integration Builder?checklist

https://www.sdn.sap.com/sdn/weblogs.sdn?blog=/pub/wlg/1688 [original link is broken] [original link is broken] [original link is broken]

also

Trouble logging to Integration Builder ( IR / ID ) ?

/people/shabarish.vijayakumar/blog/2006/02/13/unable-to-open-iresrid-xipipi-71-updated-for-pi-71-support

Regards

joel

Edited by: joel trinidade on Mar 27, 2009 3:30 PM

Answers (6)

Answers (6)

JoelTrinidade
Active Contributor
0 Kudos

There could be patch related problems check out this link.

joel

JoelTrinidade
Active Contributor
0 Kudos

There is a quick but dirty solution to get around this problem.

On your XI homepage, go to Administration page, and then choose "repository" or "directory" tab depending on which you have problem with, and then click on link "Java™ Web Start Administration". On the right side, click on button "Re-initialization and force-signing". It takes a while to initialize and re-sign all the jar files. Then you will be able to launch the repository or directory.

or

Not sure if you also tried re-deploying the 'repository.sda' application. had a similar problem where this resolved the issue. worth a shot.

or

check in

usr/sap/<SAP SID>/DVEBMGS<INSTANCE NUMBER>/j2ee/clustur/server<INSATNCE NUMBER>/apps/sap.com/com.sap.xi.repository/servlet_jsp/rep/root/start/lib

whether there is a corrupted sapj2eeclient.jar is present. if yes delete it and copy the jar from the j2eeclient directory and paste it. now restart the server...and try launching the repository.it should work...

Regards

joel

Edited by: joel trinidade on Mar 27, 2009 3:38 PM

Former Member
0 Kudos

I got into the same problem by updating the Java SDK from 1.4.2_14 to 1.4.2_20 and updating the NW Java stack (I'm not really sure which one of those two distinct updates really caused the problem.

Anyway, the "quick and dirty" solution worked fine for me, thanks. I don't really see why there's anything "dirty" about it. Simple, quick, no fussing with any Java code

JoelTrinidade
Active Contributor
0 Kudos

Hi,

When you will run the above JNLP, you will get the following Web Start exception:

JAR resources in JNLP file are not signed by same certificate

The reason for this is simple - one of the jar files that you are using was already signed by another party. Here is the way to find it:

jarsigner -certs -verbose -verify activation.jar

You will see a long list of certificates (one for each file). This means that this specific jar was signed by another party (Sun in our case). The solution for the problem is simple - put this jar in a separate JNLP and reference it in your main JNLP:

<?xml version="1.0" encoding="UTF-8"?>

<jnlp spec="1.0+" codebase="https://jaxb-workshop.dev.java.net/webstart/" href="activation.jnlp">

<information>

<title>Activation</title>

<vendor>Sun Microsystems, Inc.</vendor>

<offline-allowed/>

</information>

<offline-allowed/>

<resources>

<jar href="activation.jar"/>

</resources>

<component-desc/>

</jnlp>

As you can see, we don't ask for permissions, as this specific jar doesn't need them. Then, you reference this activation.jnlp in your main JNLP:

<?xml version="1.0" encoding="UTF-8"?>

<jnlp spec="1.0+" codebase="https://jaxb-workshop.dev.java.net/webstart/" href="wizard.jnlp">

<information>

<title>XJC Wizard</title>

<vendor>https://jaxb-workshop.dev.java.net/</vendor>

<description>Wizard frontend for XJC generator</description>

<description kind="short">Wizard frontend for XJC generator</description>

<offline-allowed/>

</information>

<offline-allowed/>

<security>

<all-permissions/>

</security>

<resources>

<j2se version="1.5+"/>

<jar href="jaxbw.jar"/>

<jar href="substance.jar"/>

<jar href="jaxb-api.jar"/>

<jar href="jaxb-impl.jar"/>

<jar href="jaxb-xjc.jar"/>

<jar href="jsr173_api.jar"/>

<extension name="activation" href="activation.jnlp"/>

</resources>

<application-desc main-class="org.jvnet.jaxbw.xjcfe.wizard.WizardMainFrame"/>

</jnlp>

regards

joel

Former Member
0 Kudos

What is your java version? If you are using XI3.0 then it should not be greater that 1.4.2_xx.

JoelTrinidade
Active Contributor
0 Kudos

Hi Sandeep,

There is an exact description of your problem statement in the blog:

Signing jars for java.net Web Start applications

http://weblogs.java.net/blog/kirillcool/archive/2005/05/signing_jars_fo.html

Regards

joel

Shabarish_Nair
Active Contributor
0 Kudos

Try Re-Initializing the Design and Configuration in Administration link of XI home page.

XI Home page -> Administration -> Javau2122 Web Start Administration

ref: /people/shabarish.vijayakumar/blog/2006/02/13/unable-to-open-iresrid-xipipi-71-updated-for-pi-71-support