So been messing with this for a while trying to get it working to no avail..

Local integration node has been created and is running (All created and started via the Console)

Node is allocated to a QM which is also running.

When im in toolkit the node is showing as down,

if i Right-Click and connect it fails saying its already running..

if i Click 'Refresh' i get the following error:-

mqsiprofile has not been run in this environment: LocalIAPIConnect (Not found in java.library.path)

Check that,

               1. The integration node is running.

               2. The TCP/IP port used by the integration node's web user interface is active.

               3. The integration node name provided in the connection details matches the name of the integration node if the node is remote.

I'm able to open the web user interface no problem.

Does anybody have any idea of what the issue is here, or other things i can try to resolve it..

Sorry if im missing important information, hopefully im not, i can answer any questions to aid getting a resolution to this.

------------------------------
Jonathan Harman
Integration Engineer
------------------------------

Hi Jonathan, 
IIBv10.0.0.10 is rather old now (that fix pack version was released in September 2017!) so unfortunately I haven't got a local installation available to check things out more closely ... but in general the Integration Nodes view in the bottom left corner of Toolkit will be automatically populated with a list of integration nodes which have been created on the same local machine as where the Toolkit installed. You can also right-click on the "Integration Nodes" level in the tree and there should be options to connect to a remote integration node. When connecting to a remote integration node you specify the Host name, port and integration node name ... and if secured you will also need to provide a user name and password. You said you were able to use a web browser to connect to the integration node - this will be using the same connection method as the dialog for making a remote node connection. So the first thing to try would be to make a remote integration node connection by filling in the Host name and port number that you were using in the URL in your web browser (or returned using mqsilist on the machine where the node is running).  I suspect this will work, given that the browser is successfully connecting ... which leads to the question why the local connection isn't successful if that's whats going wrong ... Back on that version of IIB, these local connections are made slightly differently and rely on local information on disk and in the registry about how to communicate with the node ... so I suspect it will come down to a userid issue perhaps related to the userid which the node is running under and the userid used to launch the toolkit ... or maybe to do with how Toolkit was launched and therefore not able to get access to information about the classes to load in the integration API?  This kind of thing will be difficult for me to help you with directly here, so a support ticket is the best way to do deeper diagnosis on this kind of thing, but hopefully the above pointers should give you some things to try quickly to get running (another thought ... are you trying to use a single version of the product for the Toolkit and runtime or are you attempting to mix and match across versions? ... and you didn't mention which platform you're running on either? ... and is the queue manager also started, and running under the same userid?).
Cheers,
Ben

Hello Jonathan,   

 The interesting part of the error message is that it says mqsiprofile has not been run in this environment: LocalIAPIConnect (Not found in java.library.path) which means that the toolkit will not be able to talk to the local nodes.   

How did you start the toolkit ? 

If you started the toolkit  by running eclipse.exe via a command line then instead of doing that,   run a mqsi comand console first and then start eclipse.exe from the console.  

 Regards, 

Thank you for your replies.

So after checking how it was being launched the user was launching toolkit via Eclipse.exe rather than IIBToolsLauncher.exe
Appears to look the same no matter which you open but infact it is a different environment!

All working now as expected, thank you for your help.

Regards 

Jonathan

------------------------------
Jonathan Harman
------------------------------