Please login or register to access secure site features.

Note: By continuing to use DevConnect Program Services you agree to our latest Registered Member Terms.

Sign in using DevConnect ID

Forgot password?

Trouble logging in?

Submit a ticket for Registration Support.

I have an SSO ID

?
sign in

Don't have a DevConnect or SSO ID ?

Create a DevConnect account or join the program.

register now
^
Forum Index » Avaya Orchestration Designer » Logging to an external database in modules   XML
 
Author Message
JuanMorales2



Joined: 16/12/2013 10:02:42
Messages: 44
Offline

This particular WebSphere is in a cluster, and has the libraries declared as external. We are checking with WS support, but can either of these be a problem?
WilsonYu



Joined: 06/11/2013 14:29:24
Messages: 3836
Offline

No idea what this means. Here is what I would do:

1. Define a shared library on ibm console. The definition would allow you to specify the path to library files.
2. Modify the shared library reference on each app to use the shared library.

You would have to refer to the ibm documentation for detailed steps with the admin console.
JuanMorales2



Joined: 16/12/2013 10:02:42
Messages: 44
Offline

This is how we have done it. The runtimeSupport files are copied in a directory that is then added as an external library.

JuanMorales2



Joined: 16/12/2013 10:02:42
Messages: 44
Offline

At last it worked!!!

IT turned out there is a setting on the shared library called "Use an isolated classloader for this shared library" (On the Environment -> Shared Libraries option on the menu on the left) . We changed that and it started working. This means that reports are now working, it also means that loading parameters now work.

Thank you!
WilsonYu



Joined: 06/11/2013 14:29:24
Messages: 3836
Offline

Glad you got it sorted out!
 
 
Go to: