Problems with Utilities

This chapter describes utilities-related problems.

Locale Dependency Problem With logANT

Indication:

The logANT (log analyzer) for Java-based Server log files reports an error if the log files were produced with another locale.

Reason:

Locale specific information cannot be converted properly.

Solution:

Configure the correct locale in the start script, for example:

-Duser.language=en -Duser.country=US

Run Workflow Tool Hangs

Indication:

When called from another folder, the run workflow tool hangs.

Reason:

The run workflow tool (runwf.bat or runwf.sh, respectively) does not work if it is called from a folder which is different from the location of the tool.

Solution:

In order to avoid this problem, the calling batch file must perform a cd command to the folder where the run workflow tool is located.Here is a sample snippet for Windows:

set workdir=C:\Program Files\Atos\DirX Identity\tools\utilities\workflowstarter
cd %workdir%
call runwf.bat

dirxgenpse Cannot Contact LDAP Server

Indication:

Using dirxgenpse with DirX Directory as the Connectivity store fails after some computation time.The output looks like this:

1. Search completed successfully.
2. Entries found: 1
3. Search references returned: 0
4. ldap_modify_ext_s: Can't contact LDAP server
Could not update directory entry - exiting

Reason:

The dirxgenpse utility reads the relevant LDAP directory entries before computing the PSE. Computing the relevant certificate and keys may be time-consuming especially when using a non-default length. The message indicates that the update of the relevant directory entry failed due to an LDAP connection timeout.

Solution:

Increase the LDAP connection idle time according to the DirX Directory documentation, restart the DirX Directory service, and retry the operation. After successful operation, set this idle time back to the value needed in your productive environment, then restart the DirX Directory service again. Here is a sample dirxcp command line for setting the idle time to 900 seconds:

modify cn=ldapConfiguration,o=My-Company -replaceattr ldapConnectionIdleTime=900