Hi all,

I have a problem with starting message flow after migrating configuration and services from ACE v11 to ACE v13. In one service I have a problem with the custom developer node, BIP2241E: A Loadable Implementation Library (.lil, .jar, or .par) is not found for message flow. I've copied jar files in shared-classes folder under the integration server working directory, but I have the same error. 

I need some help to resolve this.

Thanks in advance.

Hi Ranko Stanojevic,

Try to copy  the jar files at /var/mqsi/shared-classes also 

Hi all,

I have a problem with starting message flow after migrating configuration and services from ACE v11 to ACE v13. In one service I have a problem with the custom developer node, BIP2241E: A Loadable Implementation Library (.lil, .jar, or .par) is not found for message flow. I've copied jar files in shared-classes folder under the integration server working directory, but I have the same error. 

I need some help to resolve this.

Thanks in advance.

Hi all,

I have a problem with starting message flow after migrating configuration and services from ACE v11 to ACE v13. In one service I have a problem with the custom developer node, BIP2241E: A Loadable Implementation Library (.lil, .jar, or .par) is not found for message flow. I've copied jar files in shared-classes folder under the integration server working directory, but I have the same error. 

I need some help to resolve this.

Thanks in advance.

Hi all,

I have a problem with starting message flow after migrating configuration and services from ACE v11 to ACE v13. In one service I have a problem with the custom developer node, BIP2241E: A Loadable Implementation Library (.lil, .jar, or .par) is not found for message flow. I've copied jar files in shared-classes folder under the integration server working directory, but I have the same error. 

I need some help to resolve this.

Thanks in advance.

Hi Ranko

You also can set a specific project or directory as you source for those loadable implementations via the any of the below properties in your server.conf.yaml, for standalone integration servers. You can point that to a library that you can deploy or to a shared directory.

#lilPath: '' # A list of paths from where User-defined node LIL/JAR files are loaded. (multiple directories are separated by platform path separator)









#additionalJpluginDirectories: '' # Extra directories to search for Java plugins; can reference shared libraries using '{shlibname}' syntax.





#additionalSharedClassesDirectories: '' # Extra directories to add to the shared classloader search path; can reference shared libraries using '{shlibname}' syntax.

ACEv13 nodes also have the lilPath as an option in the node.conf.yaml.

Personally, I install my udn's in the server\jplugin, like Bural also suggested.

------------------------------
Regards
Matthias Blomme
Integration Specialist
Integration Designers
Turnhout

Original Message:
Sent: Fri July 25, 2025 05:04 AM
From: Ranko Stanojevic
Subject: ACE migration v11 to v13 problem

Hi all,

I have a problem with starting message flow after migrating configuration and services from ACE v11 to ACE v13. In one service I have a problem with the custom developer node, BIP2241E: A Loadable Implementation Library (.lil, .jar, or .par) is not found for message flow. I've copied jar files in shared-classes folder under the integration server working directory, but I have the same error. 

I need some help to resolve this.

Thanks in advance.

------------------------------
Ranko Stanojevic
------------------------------

Thanks Matthias for your response.

I've put this in server.conf.yaml of integration server

lilPath: '/home/cloud-user/user-defined-extension-files/'
#additionalJpluginDirectories: '' # Extra directories to search for Java plugins; can reference shared libraries using '{shlibname}' syntax.
additionalJpluginDirectories: '/home/cloud-user/user-defined-extension-files/'

#additionalSharedClassesDirectories: '' # Extra directories to add to the shared classloader search path; can reference shared libraries using '{shlibname}' syntax.
additionalSharedClassesDirectories: '/home/cloud-user/user-defined-extension-files/'

But still the same error after node restart.

Problem with installation of this udn is that I didn't implement this and I only have .jar files from old system. I've tried to put them in same location like the old one, but it seems that ACE v13 has some problem reading it.

If you read documentation Installing user-defined extension runtime files on an integration server

It says that if I want to install my compiled or packaged user-defined extension file (files with extension .lil, .jar, .par, .pdb, or .lel), I need to put it in some directory with chmod 755, and to add that directory to the LILPATH by updating the server.conf.yaml configuration file. After restart of integration server, it should load user-defined extension files during initialization.

I've done all steps, but still the same error when starting message flow with this udn.

------------------------------
Ranko Stanojevic

Original Message:
Sent: Tue September 02, 2025 03:02 AM
From: Matthias Blomme
Subject: ACE migration v11 to v13 problem

Hi Ranko

You also can set a specific project or directory as you source for those loadable implementations via the any of the below properties in your server.conf.yaml, for standalone integration servers. You can point that to a library that you can deploy or to a shared directory.

#lilPath: '' # A list of paths from where User-defined node LIL/JAR files are loaded. (multiple directories are separated by platform path separator)
#additionalJpluginDirectories: '' # Extra directories to search for Java plugins; can reference shared libraries using '{shlibname}' syntax.
#additionalSharedClassesDirectories: '' # Extra directories to add to the shared classloader search path; can reference shared libraries using '{shlibname}' syntax.

ACEv13 nodes also have the lilPath as an option in the node.conf.yaml.

Personally, I install my udn's in the server\jplugin, like Bural also suggested.

------------------------------
Regards
Matthias Blomme
Integration Specialist
Integration Designers
Turnhout

Original Message:
Sent: Fri July 25, 2025 05:04 AM
From: Ranko Stanojevic
Subject: ACE migration v11 to v13 problem

Hi all,

I have a problem with starting message flow after migrating configuration and services from ACE v11 to ACE v13. In one service I have a problem with the custom developer node, BIP2241E: A Loadable Implementation Library (.lil, .jar, or .par) is not found for message flow. I've copied jar files in shared-classes folder under the integration server working directory, but I have the same error. 

I need some help to resolve this.

Thanks in advance.

------------------------------
Ranko Stanojevic
------------------------------

Hi Ranko

Not much more I can do at the moment. For me it has always worked by using the lilPath or addistionalJpluginDirectories or by using the server\jplugin directory. Both on my local machines and my servers.

You do need to make sure those directories are readable. You could try to enable tracing, to see if you get more output.

Other than that, unless you are willing to share your setup (via dm or otherwise) not much more I can tell you .

Thanks Matthias for your response.

I've put this in server.conf.yaml of integration server

lilPath: '/home/cloud-user/user-defined-extension-files/'
#additionalJpluginDirectories: '' # Extra directories to search for Java plugins; can reference shared libraries using '{shlibname}' syntax.
additionalJpluginDirectories: '/home/cloud-user/user-defined-extension-files/'

#additionalSharedClassesDirectories: '' # Extra directories to add to the shared classloader search path; can reference shared libraries using '{shlibname}' syntax.
additionalSharedClassesDirectories: '/home/cloud-user/user-defined-extension-files/'

But still the same error after node restart.

Problem with installation of this udn is that I didn't implement this and I only have .jar files from old system. I've tried to put them in same location like the old one, but it seems that ACE v13 has some problem reading it.

If you read documentation Installing user-defined extension runtime files on an integration server

It says that if I want to install my compiled or packaged user-defined extension file (files with extension .lil, .jar, .par, .pdb, or .lel), I need to put it in some directory with chmod 755, and to add that directory to the LILPATH by updating the server.conf.yaml configuration file. After restart of integration server, it should load user-defined extension files during initialization.

I've done all steps, but still the same error when starting message flow with this udn.

------------------------------
Ranko Stanojevic

Original Message:
Sent: Tue September 02, 2025 03:02 AM
From: Matthias Blomme
Subject: ACE migration v11 to v13 problem

Hi Ranko

You also can set a specific project or directory as you source for those loadable implementations via the any of the below properties in your server.conf.yaml, for standalone integration servers. You can point that to a library that you can deploy or to a shared directory.

#lilPath: '' # A list of paths from where User-defined node LIL/JAR files are loaded. (multiple directories are separated by platform path separator)
#additionalJpluginDirectories: '' # Extra directories to search for Java plugins; can reference shared libraries using '{shlibname}' syntax.
#additionalSharedClassesDirectories: '' # Extra directories to add to the shared classloader search path; can reference shared libraries using '{shlibname}' syntax.

ACEv13 nodes also have the lilPath as an option in the node.conf.yaml.

Personally, I install my udn's in the server\jplugin, like Bural also suggested.

------------------------------
Regards
Matthias Blomme
Integration Specialist
Integration Designers
Turnhout

Original Message:
Sent: Fri July 25, 2025 05:04 AM
From: Ranko Stanojevic
Subject: ACE migration v11 to v13 problem

Hi all,

I have a problem with starting message flow after migrating configuration and services from ACE v11 to ACE v13. In one service I have a problem with the custom developer node, BIP2241E: A Loadable Implementation Library (.lil, .jar, or .par) is not found for message flow. I've copied jar files in shared-classes folder under the integration server working directory, but I have the same error. 

I need some help to resolve this.

Thanks in advance.

------------------------------
Ranko Stanojevic
------------------------------