Home

Results 1 to 5 of 5

Thread: UserApplication Client configuration issue.

  1. #1
    Join Date
    Mar 2016
    Posts
    82

    UserApplication Client configuration issue.

    Our situation:
    We have 2 UA servers. We wanted to store the client settings in the DB. We altered the ism-configuration.properties file based on the documentation provided by MF. So the issues we have now encountered are:
    Dashboard no longer loads and throws the error: Internal Error. Please contact Administrator.
    The cache settings are completely wiped out and can no longer flush the cache.
    Cluster mode can't be enabled.
    Administrator assignments seem to have been corrupted or altered in some odd way.
    User search function now fails.

    Has anyone sucessfully changed from file system mode to database mode without seeing a wide array of errors?

    Our environment
    RHEL 7
    Idvault 4.7.2
    UA version 4.7.2
    eDir 9.1.2

  2. #2
    Join Date
    Jan 2009
    Location
    Stavanger, Norway
    Posts
    1,729

    Re: UserApplication Client configuration issue.

    jburns80 <jburns80@no-mx.forums.microfocus.com> wrote:
    >

    Our situation:
    > We have 2 UA servers. We wanted to store the client settings in the DB.

    We altered the ism-configuration.properties file based on the
    documentation provided by MF. So the issues we have now encountered
    are:
    > Dashboard no longer loads and throws the error: Internal Error. Please

    contact Administrator.
    > The cache settings are completely wiped out and can no longer flush the

    cache.
    > Cluster mode can't be enabled.
    > Administrator assignments seem to have been corrupted or altered in some

    odd way.
    > User search function now fails.
    >
    > Has anyone sucessfully changed from file system mode to database mode

    without seeing a wide array of errors?
    >


    Yes. Same environment as you except UA 4.7.1.1

    This can be tricky to get right.

    You need to add two lines to ism-configuration.properties

    com.netiq.idmdash.client.settings.store.preference = database

    And

    com.netiq.idm.rbpm.updateConfig-On-StartUp = true

    Clear your browser cache. Then restart tomcat.


    One tells

  3. #3
    Join Date
    Mar 2016
    Posts
    82

    Re: UserApplication Client configuration issue.

    That didn't seem to help. Looks like when changing the client setting to Database something got screwy with the settings, I see this error in the logs: Caused by: com.netiq.idm.settings.AdminClientSettingsExceptio n: Client Not Found.

  4. #4
    Join Date
    Mar 2016
    Posts
    82

    Re: UserApplication Client configuration issue.

    It seems like the default client is not getting properly applied with switching to the Database option for the client settings.

  5. #5
    Join Date
    Jan 2009
    Location
    Stavanger, Norway
    Posts
    1,729

    Re: UserApplication Client configuration issue.

    jburns80 wrote:

    >
    > It seems like the default client is not getting properly applied with
    > switching to the Database option for the client settings.


    Did you get this to work in the end?
    I recall I had to tweak some stuff directly in the DB in one instance to get
    this to work.

    --
    If you find this post helpful, and are viewing this using the web, please show
    your appreciation by clicking on the star below

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •