ASG
IBM
Zystems
Cressida
Icon
Netflexity
 
  MQSeries.net
Search  Search       Tech Exchange      Education      Certifications      Library      Info Center      SupportPacs      LinkedIn  Search  Search                                                                   FAQ  FAQ   Usergroups  Usergroups
 
Register  ::  Log in Log in to check your private messages
 
RSS Feed - WebSphere MQ Support RSS Feed - Message Broker Support

MQSeries.net Forum Index » WebSphere Message Broker (ACE) Support » Problem in WSDL import [SOLVED]

Post new topic  Reply to topic
 Problem in WSDL import [SOLVED] « View previous topic :: View next topic » 
Author Message
Sabina
PostPosted: Mon Oct 17, 2016 9:35 pm    Post subject: Problem in WSDL import [SOLVED] Reply with quote

Novice

Joined: 27 Sep 2016
Posts: 14

Hello everyone,

I encountered a problem while importing a wsdl file (from external url) for message model. I suspect that it is due to SSL certificates. But my keystore and trustore are already configured and all the necessary certificates are in there.

Please, help, I don't know how to troubleshoot this problem.

There is no warning or error after I paste the url. But the "next" button doesn't get active anyway.

Here is the screenshot: https://drive.google.com/open?id=0B8mzD9CYC0gVa2oyaG9aUmFlZEE


Last edited by Sabina on Tue Oct 18, 2016 4:21 am; edited 1 time in total
Back to top
View user's profile Send private message
martinb
PostPosted: Mon Oct 17, 2016 11:08 pm    Post subject: Reply with quote

Master

Joined: 09 Nov 2006
Posts: 210
Location: UK

Have you looked for any error reported to the Eclipse Error log?

Main menu Window -> Show view -> Other -> Errors
Back to top
View user's profile Send private message
Sabina
PostPosted: Mon Oct 17, 2016 11:38 pm    Post subject: Reply with quote

Novice

Joined: 27 Sep 2016
Posts: 14

martinb wrote:
Have you looked for any error reported to the Eclipse Error log?

Main menu Window -> Show view -> Other -> Errors


No, unfortunately, no errors were there
Back to top
View user's profile Send private message
Sabina
PostPosted: Mon Oct 17, 2016 11:42 pm    Post subject: Reply with quote

Novice

Joined: 27 Sep 2016
Posts: 14

So, I have found a good piece of information here: http://www.ibm.com/support/knowledgecenter/SSMKHH_9.0.0/com.ibm.etools.mft.doc/bd13710_.htm

But here occurred a new problem. I get an error at step 7, when trying this command:

mb -vmargs -Djavax.net.ssl.trustStore=d:\\mb.keystore
-Djavax.net.ssl.trustStorePassword=broker

The error is: "Could not create the Java Virtual Machine. A fatal exception occurred. Program will exit".

No idea why
Back to top
View user's profile Send private message
Sabina
PostPosted: Tue Oct 18, 2016 12:25 am    Post subject: Reply with quote

Novice

Joined: 27 Sep 2016
Posts: 14

Update: I figured out what was wrong with the command and it completed successfully. But... The problem with WSDL persists anyway.
Back to top
View user's profile Send private message
martinb
PostPosted: Tue Oct 18, 2016 12:28 am    Post subject: Reply with quote

Master

Joined: 09 Nov 2006
Posts: 210
Location: UK

Good those steps will create a truststore for you to import the cert you need the IIB Toolkit Eclipse JVM to trust.

Are you sure you have returned to the Toolkit install directory before you run the "mb" command to start it?

An alternative to starting the IIB toolkit manually with the "mb" command and the vmargs parameters for the trust store, is to add these to the "eclipse.ini" file. Note this will mean that every time you start the Toolkit it will have that trust store installed, so you may wish to remove them again after you've completed the import.
Back to top
View user's profile Send private message
timber
PostPosted: Tue Oct 18, 2016 12:31 am    Post subject: Reply with quote

Grand Master

Joined: 25 Aug 2015
Posts: 1292

I suggest that you download the WSDL and store it on your local drive. Then import it from there. If the download fails, at least it might give better diagnostics than the IIB toolkit.
Back to top
View user's profile Send private message
Sabina
PostPosted: Tue Oct 18, 2016 2:35 am    Post subject: Reply with quote

Novice

Joined: 27 Sep 2016
Posts: 14

martinb wrote:
Good those steps will create a truststore for you to import the cert you need the IIB Toolkit Eclipse JVM to trust.

Are you sure you have returned to the Toolkit install directory before you run the "mb" command to start it?

An alternative to starting the IIB toolkit manually with the "mb" command and the vmargs parameters for the trust store, is to add these to the "eclipse.ini" file. Note this will mean that every time you start the Toolkit it will have that trust store installed, so you may wish to remove them again after you've completed the import.


Yes, successful command completion triggered toolkit start.

I tried to add my keystore and truststore options to the "eclipse.ini" file, but exception got out.

Here is screenshot: https://drive.google.com/open?id=0B8mzD9CYC0gVQmdSQ3JHYm1WZUE
Back to top
View user's profile Send private message
Sabina
PostPosted: Tue Oct 18, 2016 2:36 am    Post subject: Reply with quote

Novice

Joined: 27 Sep 2016
Posts: 14

timber wrote:
I suggest that you download the WSDL and store it on your local drive. Then import it from there. If the download fails, at least it might give better diagnostics than the IIB toolkit.


I guess that's what I will have to do
Back to top
View user's profile Send private message
Sabina
PostPosted: Tue Oct 18, 2016 2:51 am    Post subject: Reply with quote

Novice

Joined: 27 Sep 2016
Posts: 14

Sabina wrote:
martinb wrote:
Good those steps will create a truststore for you to import the cert you need the IIB Toolkit Eclipse JVM to trust.

Are you sure you have returned to the Toolkit install directory before you run the "mb" command to start it?

An alternative to starting the IIB toolkit manually with the "mb" command and the vmargs parameters for the trust store, is to add these to the "eclipse.ini" file. Note this will mean that every time you start the Toolkit it will have that trust store installed, so you may wish to remove them again after you've completed the import.


Yes, successful command completion triggered toolkit start.

I tried to add my keystore and truststore options to the "eclipse.ini" file, but exception got out.

Here is screenshot: https://drive.google.com/open?id=0B8mzD9CYC0gVQmdSQ3JHYm1WZUE


Figured it out!!!!!

I made some mistakes in the file. After launching toolkit my wsdl successfully got imported.
Back to top
View user's profile Send private message
Display posts from previous:   
Post new topic  Reply to topic Page 1 of 1

MQSeries.net Forum Index » WebSphere Message Broker (ACE) Support » Problem in WSDL import [SOLVED]
Jump to:  



You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
Protected by Anti-Spam ACP
 
 


Theme by Dustin Baccetti
Powered by phpBB © 2001, 2002 phpBB Group

Copyright © MQSeries.net. All rights reserved.