Changed admin password, now cannot start user application


I have recently changed the admin password for the tree running our user
application. Since then I have been unable to start the user
application. The error in the jboss.log says unable to log in as admin.
After reading other posts on this topic, I have tried redeploying my
user application driver with the new password and that has not helped.
Is there a configuration file that is stored that needs to be updated
with the new password?

Server running SLES10
IDM version 3.6.1


--
kimlamon
------------------------------------------------------------------------
kimlamon's Profile: http://forums.novell.com/member.php?userid=66875
View this thread: http://forums.novell.com/showthread.php?t=448189

  • On 11/14/2011 12:36 PM, kimlamon wrote:
    >
    > I have recently changed the admin password for the tree running our user
    > application. Since then I have been unable to start the user
    > application. The error in the jboss.log says unable to log in as admin.
    > After reading other posts on this topic, I have tried redeploying my
    > user application driver with the new password and that has not helped.
    > Is there a configuration file that is stored that needs to be updated
    > with the new password?
    >
    > Server running SLES10
    > IDM version 3.6.1
    >
    >

    Greetings,
    Yes there is a configuration tool, and its name is configupdate
    (.bat or .sh depending on the O/S). You will need to launch this tool
    and enter the eDir Admin's password and then press OK. Then you should
    be able to start jBoss successfully.

    configupdate is located in the "root" of the User Application install
    folder. It is where the start-jboss and stop-jboss scripts will be
    located. For example: /opt/novell/idm



    --
    Sincerely,
    Steven Williams
    Lead Software Engineer
    NetIQ

  • Thank you. I was able to find the config script but getting the
    following error when starting it. Exception in thread "main"
    java.lang.ExceptionInInitializerError
    at
    com.novell.internal.installer.idm.ldap.LdapConfig.config(LdapConfig.java:577)
    at
    com.novell.internal.installer.idm.ldap.LdapConfig.main(LdapConfig.java:192)
    Caused by: java.awt.HeadlessException:
    No X11 DISPLAY variable was set, but this program performed an
    operation which requires it.
    at sun.awt.HeadlessToolkit.getScreenSize(Unknown Source)
    at
    com.novell.internal.installer.idm.ldap.LdapConfigScreen.<clinit>(LdapConfigScreen.java:123)
    ... 2 more


    --
    kimlamon
    ------------------------------------------------------------------------
    kimlamon's Profile: http://forums.novell.com/member.php?userid=66875
    View this thread: http://forums.novell.com/showthread.php?t=448189

  • On 11/14/2011 12:56 PM, kimlamon wrote:
    >
    > Thank you. I was able to find the config script but getting the
    > following error when starting it. Exception in thread "main"
    > java.lang.ExceptionInInitializerError
    > at
    > com.novell.internal.installer.idm.ldap.LdapConfig.config(LdapConfig.java:577)
    > at
    > com.novell.internal.installer.idm.ldap.LdapConfig.main(LdapConfig.java:192)
    > Caused by: java.awt.HeadlessException:
    > No X11 DISPLAY variable was set, but this program performed an
    > operation which requires it.
    > at sun.awt.HeadlessToolkit.getScreenSize(Unknown Source)
    > at
    > com.novell.internal.installer.idm.ldap.LdapConfigScreen.<clinit>(LdapConfigScreen.java:123)
    > .. 2 more
    >
    >

    Greetings,
    configupdate is going to launch a gui console. If you are
    receiving the above then you X.

    A) Go onto the Linux machine itself and run a runlevel 5 (if X is installed)

    B) Redirect X to another machine (X has to be installed on the host server)

    C) Or, you need to set configupdate to run in console mode..

    for 361 UA:

    1) Open configupdate.sh in an editor (my favorite is vi)
    2) scroll down to the bottom. The top has information
    3) In the command you will see -stop_deployer false
    4) Right after that enter the following: -use_console true
    5) Make sure to give a space on either side
    6) Save
    7) start configupdate, it will be in console mode



    --
    Sincerely,
    Steven Williams
    Lead Software Engineer
    NetIQ