Details
-
Type:
Bug
-
Status:
Closed
-
Priority:
Blocker
-
Resolution: Fixed
-
Affects Version/s: None
-
Fix Version/s: 3.2.2 (EE only), 3.3.0
-
Component/s: Core: Bootstrap / Standalone
-
Labels:
-
User impact:Medium
-
Similar Issues:None
Description
The SAP transport is a challenge for Studio and iON. It uses SAP JCo libraries that depend on native libraries (dll, so, nlib, etc)
The problem is that right now, the only way to configure this in Mule ESB is:
1) Adding the jco jar file and the native library in $MULE_HOME/lib/opt
2) Changing the wrapper.conf file
3) Setting the OS environment variable LD_LIBRARY_PATH
For iON and Studio this is a problem as additional configuration outside the application should be done. It will be really easy if all of this files (mule-transport-sap.jar, jco.jar, idoc.jar and jco.so) can be packed inside the ${app.home}/lib directory and Mule will use them from there.
We can check: http://nicklothian.com/blog/2008/11/19/modify-javalibrarypath-at-runtime/ and/or http://fahdshariff.blogspot.com/2011/08/changing-java-library-path-at-runtime.html
Another option is that when deploying the app, the deployer will copy native libraries to a known path already pre-configured at startup by default. The only problem is that the undeploy and redeploy should check if that library should be replaced or removed.
Activity
| Field | Original Value | New Value |
|---|---|---|
| Description |
The SAP transport is a challenge for Studio and iON. It uses SAP JCo libraries that depend on native libraries (dll, so, nlib, etc)
The problem is that right now, the only way to configure this in Mule ESB is: 1) Adding the jco jar file and the native library in $MULE_HOME/lib/opt 2) Changing the wrapper.conf file 3) Setting the OS environment variable LD_LIBRARY_PATH For iON and Studio this is a problem as additional configuration outside the application should be done. It will be really easy if all of this files (mule-transport-sap.jar, jco.jar, idoc.jar and jco.so) can be packed inside the ${app.home}/lib directory and Mule will use them from there. We can check: http://nicklothian.com/blog/2008/11/19/modify-javalibrarypath-at-runtime/ Another option is that when deploying the app, the deployer will copy native libraries to a known path already pre-configured at startup by default. The only problem is that the undeploy and redeploy should check if that library should be replaced or removed. |
The SAP transport is a challenge for Studio and iON. It uses SAP JCo libraries that depend on native libraries (dll, so, nlib, etc)
The problem is that right now, the only way to configure this in Mule ESB is: 1) Adding the jco jar file and the native library in $MULE_HOME/lib/opt 2) Changing the wrapper.conf file 3) Setting the OS environment variable LD_LIBRARY_PATH For iON and Studio this is a problem as additional configuration outside the application should be done. It will be really easy if all of this files (mule-transport-sap.jar, jco.jar, idoc.jar and jco.so) can be packed inside the ${app.home}/lib directory and Mule will use them from there. We can check: http://nicklothian.com/blog/2008/11/19/modify-javalibrarypath-at-runtime/ and/or http://fahdshariff.blogspot.com/2011/08/changing-java-library-path-at-runtime.html Another option is that when deploying the app, the deployer will copy native libraries to a known path already pre-configured at startup by default. The only problem is that the undeploy and redeploy should check if that library should be replaced or removed. |
| Labels | SAP-Transport, | SAP-Transport |
| Fix Version/s | 3.3.0 [ 11110 ] | |
| Assignee | Daniel Feist [ dfeist ] |
| Priority | To be reviewed [ 6 ] | Blocker [ 1 ] |
| Attachment | mule-module-launcher-3.3-M3.jar [ 15344 ] | |
| Attachment | mule-module-launcher-3.2.2.jar [ 15343 ] |
| Resolution | Fixed [ 1 ] | |
| Fix Version/s | 3.2.2 (EE only) [ 11105 ] | |
| Assignee | Daniel Feist [ dfeist ] | Pablo Kraan [ pablo.kraan ] |
| Status | Open [ 1 ] | Closed [ 6 ] |