Generic Driver and Remote Load


Hello Everyone.

Hope your new year has started out well.

I've been reconfiguring my DLT drivers to use the Generic Text Driver.
And I started to have an issue with the remoter loader.

I'm seeing this in the log file.

DirXML Log Event -------------------
Thread = Loader
Level = fatal
Message = Unable to create driver: java.lang.ClassNotFoundException:
C:\Novell\RemoteLoader\64bit\lib\GenFileDriverShim_0.9.jar

Here's what my config file looks like;

-description "genParDLT"
-commandport 8001
-connection "port=8091"
-trace 5
-tracefile "C:\novell\remoteloader\64bit\genParDLT-Trace.log"
-tracefilemax 4096M
-class "C:\Novell\RemoteLoader\64bit\lib\GenFileDriverShim_0.9.jar"


Am I missing something?

Would anyone know if there are configuration instructions for setting up
the Remote Loader with the Generic driver.

Any suggestions are appreciated.

Allen


--
allenmorris
------------------------------------------------------------------------
allenmorris's Profile: https://forums.netiq.com/member.php?userid=1565
View this thread: https://forums.netiq.com/showthread.php?t=55311

  • On 2/4/2016 12:54 PM, allenmorris wrote:
    >
    > Hello Everyone.
    >
    > Hope your new year has started out well.
    >
    > I've been reconfiguring my DLT drivers to use the Generic Text Driver.
    > And I started to have an issue with the remoter loader.
    >
    > I'm seeing this in the log file.
    >
    > DirXML Log Event -------------------
    > Thread = Loader
    > Level = fatal
    > Message = Unable to create driver: java.lang.ClassNotFoundException:
    > C:\Novell\RemoteLoader\64bit\lib\GenFileDriverShim_0.9.jar
    >
    > Here's what my config file looks like;
    >
    > -description "genParDLT"
    > -commandport 8001
    > -connection "port=8091"
    > -trace 5
    > -tracefile "C:\novell\remoteloader\64bit\genParDLT-Trace.log"
    > -tracefilemax 4096M
    > -class "C:\Novell\RemoteLoader\64bit\lib\GenFileDriverShim_0.9.jar"
    >
    >
    > Am I missing something?
    >
    > Would anyone know if there are configuration instructions for setting up
    > the Remote Loader with the Generic driver.
    >
    > Any suggestions are appreciated.
    >
    > Allen
    >
    >

    Silly question but does the driver shim jar exist where it is looking?
    Next thing I would say is look at the permissions for the remote loader user. Later windows versions are picky about
    permissions and the user that the remote loader is running as may not have rights to read it.
    If you turn up the trace do you get a longer stack trace? Could be a dependent jar file that is missing.

    --
    -----------------------------------------------------------------------
    Will Schneider
    Knowledge Partner http://forums.netiq.com

    If you find this post helpful, please click on the star below.
  • No, this is not it. The windows RL is a mess because it's basically the
    only one used where a "module" vs. a "class" type of RL is used. In this
    case a "class" is specified, but then a JAR file is the thin referenced.
    Always use a class (com.novell.dirxml.driver.whatever) when it asks for a
    class. In this case, use the proper class for that particular shim, which
    you can either find by breaking open the JAR or probably by looking at its
    homepage/CoolSolution.

    --
    Good luck.

    If you find this post helpful and are logged into the web interface,
    show your appreciation and click on the star below...
  • allenmorris wrote:

    > -class "C:\Novell\RemoteLoader\64bit\lib\GenFileDriverShim_0.9.jar"


    As Aaron already pointed out, use a class name not a Java ARchive file
    name/path, in case of the Generic File Driver it's:
    info.vancauwenberge.filedriver.shim.driver.GenericFileDriverShim

    Here's my (Linux and Java) remoteloader config template you may find handy for
    future use. Even on Windows you can ditch the buggy rlconsole.exe and use it
    with the pure java remote loader (Geoffrey has written an excellent article
    about the different flavors of RLs in existence, btw. - you'll find it
    somewhere on cool solutions).

    ################################################################################
    # configuration file for rdxml or dirxml_jremote. See
    # https://www.netiq.com/documentation/idm402/idm_remoteloader/data/bs35pjx.html
    # for descriptions and explanations of available parameters.
    ################################################################################

    # used for the trace window title and for Novell Audit logging
    -description RemoteLoaderTemplate

    -commandport 8000
    -connection "port=8090"
    # when using on the engine server:
    # -connection "port=8090 address=127.0.0.1 fromaddress=127.0.0.1"
    # when using SSL:
    # -connection "port=8090 keystore=<keystorename> storepass=<password>"

    # Custom Java parameter examples:
    # -javaparam DHOST_JVM_MAX_HEAP=512M
    # -javaparam "DHOST_JVM_OPTIONS=-Dfile.encoding=utf-8 -Duser.language=en"

    -trace 4
    -tracefile /var/log/idm/trace/remoteloadertemplate.log
    -tracefilemax 100M

    # uncomment the shim to use. IMPORTANT: make sure no leading space exists
    before "-class" !
    # -class be.opns.dirxml.driver.ars.arsremedydrivershim.ARSDriverShim
    # -class com.novell.gw.dirxml.driver.gw.GWdriverShim
    # -class com.novell.idm.driver.ComposerDriverShim
    # -class com.novell.idm.drivers.idprovider.IDProviderShim
    # -class com.novell.nds.dirxml.driver.avaya.PBXDriverShim
    # -class com.novell.nds.dirxml.driver.dcsshim.DCSShim
    # -class com.novell.nds.dirxml.driver.delimitedtext.DelimitedTextDriver
    # -class com.novell.nds.dirxml.driver.entitlement.EntitlementServiceDriver
    # -class com.novell.nds.dirxml.driver.jdbc.JDBCDriverShim
    # -class com.novell.nds.dirxml.driver.jms.JMSDriverShim
    # -class com.novell.nds.dirxml.driver.ldap.LDAPDriverShim
    # -class com.novell.nds.dirxml.driver.loopback.LoopbackDriverShim
    # -class com.novell.nds.dirxml.driver.manualtask.driver.ManualTaskDriver
    # -class com.novell.nds.dirxml.driver.msgateway.MSGatewayDriverShim
    # -class com.novell.nds.dirxml.driver.nisdriver.NISDriverShim
    # -class com.novell.nds.dirxml.driver.notes.NotesDriverShim
    # -class com.novell.nds.dirxml.driver.psoftshim.PSOFTDriverShim
    # -class com.novell.nds.dirxml.driver.salesforce.SFDriverShim
    # -class com.novell.nds.dirxml.driver.sap.portal.SAPPortalShim
    # -class com.novell.nds.dirxml.driver.SAPHRShim.SAPDriverShim
    # -class com.novell.nds.dirxml.driver.sapumshim.SAPDriverShim
    # -class com.novell.nds.dirxml.driver.soap.SOAPDriver
    # -class com.novell.nds.dirxml.driver.workorder.WorkOrderDriverShim
    # -class info.vancauwenberge.filedriver.shim.driver.GenericFileDriverShim

    --
    http://www.is4it.de/en/solution/identity-access-management/
  • On 2/4/2016 2:02 PM, ab wrote:
    > No, this is not it. The windows RL is a mess because it's basically the
    > only one used where a "module" vs. a "class" type of RL is used. In this
    > case a "class" is specified, but then a JAR file is the thin referenced.
    > Always use a class (com.novell.dirxml.driver.whatever) when it asks for a
    > class. In this case, use the proper class for that particular shim, which
    > you can either find by breaking open the JAR or probably by looking at its
    > homepage/CoolSolution.


    Or drop a Packaged version into Designer on a tree, and you will see it is:

    info.vancauwenberge.filedriver.shim.driver.GenericFileDriverShim



  • > Here's my (Linux and Java) remoteloader config template you may find handy for
    > future use. Even on Windows you can ditch the buggy rlconsole.exe and use it
    > with the pure java remote loader (Geoffrey has written an excellent article
    > about the different flavors of RLs in existence, btw. - you'll find it
    > somewhere on cool solutions).


    Beetlejuice, beetlejuice, BEETLEJUICE!!!!

    http://www.novell.com/communities/node/2994/many-faces-remote-loaders-idm




    > ################################################################################
    > # configuration file for rdxml or dirxml_jremote. See
    > # https://www.netiq.com/documentation/idm402/idm_remoteloader/data/bs35pjx.html
    > # for descriptions and explanations of available parameters.
    > ################################################################################
    >
    > # used for the trace window title and for Novell Audit logging
    > -description RemoteLoaderTemplate
    >
    > -commandport 8000
    > -connection "port=8090"
    > # when using on the engine server:
    > # -connection "port=8090 address=127.0.0.1 fromaddress=127.0.0.1"
    > # when using SSL:
    > # -connection "port=8090 keystore=<keystorename> storepass=<password>"
    >
    > # Custom Java parameter examples:
    > # -javaparam DHOST_JVM_MAX_HEAP=512M
    > # -javaparam "DHOST_JVM_OPTIONS=-Dfile.encoding=utf-8 -Duser.language=en"
    >
    > -trace 4
    > -tracefile /var/log/idm/trace/remoteloadertemplate.log
    > -tracefilemax 100M
    >
    > # uncomment the shim to use. IMPORTANT: make sure no leading space exists
    > before "-class" !
    > # -class be.opns.dirxml.driver.ars.arsremedydrivershim.ARSDriverShim
    > # -class com.novell.gw.dirxml.driver.gw.GWdriverShim
    > # -class com.novell.idm.driver.ComposerDriverShim
    > # -class com.novell.idm.drivers.idprovider.IDProviderShim
    > # -class com.novell.nds.dirxml.driver.avaya.PBXDriverShim
    > # -class com.novell.nds.dirxml.driver.dcsshim.DCSShim
    > # -class com.novell.nds.dirxml.driver.delimitedtext.DelimitedTextDriver
    > # -class com.novell.nds.dirxml.driver.entitlement.EntitlementServiceDriver
    > # -class com.novell.nds.dirxml.driver.jdbc.JDBCDriverShim
    > # -class com.novell.nds.dirxml.driver.jms.JMSDriverShim
    > # -class com.novell.nds.dirxml.driver.ldap.LDAPDriverShim
    > # -class com.novell.nds.dirxml.driver.loopback.LoopbackDriverShim
    > # -class com.novell.nds.dirxml.driver.manualtask.driver.ManualTaskDriver
    > # -class com.novell.nds.dirxml.driver.msgateway.MSGatewayDriverShim
    > # -class com.novell.nds.dirxml.driver.nisdriver.NISDriverShim
    > # -class com.novell.nds.dirxml.driver.notes.NotesDriverShim
    > # -class com.novell.nds.dirxml.driver.psoftshim.PSOFTDriverShim
    > # -class com.novell.nds.dirxml.driver.salesforce.SFDriverShim
    > # -class com.novell.nds.dirxml.driver.sap.portal.SAPPortalShim
    > # -class com.novell.nds.dirxml.driver.SAPHRShim.SAPDriverShim
    > # -class com.novell.nds.dirxml.driver.sapumshim.SAPDriverShim
    > # -class com.novell.nds.dirxml.driver.soap.SOAPDriver
    > # -class com.novell.nds.dirxml.driver.workorder.WorkOrderDriverShim
    > # -class info.vancauwenberge.filedriver.shim.driver.GenericFileDriverShim


    This is quite a clever approach. :) One config file to rule them all.
    As usual from Lothar... Darn Australians are clever.

  • It feels so good when you can predict the future... :-)
  • On 2/4/2016 2:45 PM, Lothar Haeger wrote:
    > It feels so good when you can predict the future... :-)


    The word you were looking for is predictable. :)

    I am like that stupid URL shortener. But rather a URL lengthener. But
    only in a specific domain.

  • Geoffrey Carman wrote:

    > http://www.novell.com/communities/node/2994/many-faces-remote-loaders-idm


    ..NET remote loader? Scripting Driver's embedded (crappy non-standard
    incomplete) RL? Time for a reprint....

    --
    http://www.is4it.de/en/solution/identity-access-management/

  • Thank you all powerful wizards of the cloud...

    Your words will be put to good use.

    Allen


    --
    allenmorris
    ------------------------------------------------------------------------
    allenmorris's Profile: https://forums.netiq.com/member.php?userid=1565
    View this thread: https://forums.netiq.com/showthread.php?t=55311

  • On 2/4/2016 3:26 PM, Lothar Haeger wrote:
    > Geoffrey Carman wrote:
    >
    >> http://www.novell.com/communities/node/2994/many-faces-remote-loaders-idm

    >
    > .NET remote loader? Scripting Driver's embedded (crappy non-standard
    > incomplete) RL? Time for a reprint....


    Come on, I wrote that in 2007. Amazing how well it held up for the
    most part.