CA LDAP starts up but appears dormant

book

Article ID: 144572

calendar_today

Updated On:

Products

CA ACF2 CA ACF2 - DB2 Option CA ACF2 for zVM CA ACF2 - z/OS CA ACF2 - MISC

Issue/Introduction

An LDAP Server STC is started but it quickly appears dormant - no messages are seen after HASP373 LDAPSRVR STARTED.

 

Environment

Release : 16.0

Component : CA ACF2 for z/OS

Resolution

Inspection of CA LDAP Server slapd.conf and slap.env files from the CA LDAP Server installation directory showed there were no
uncommented 'moduleload' statements activated or coded for the backend interface for which the CA LDAP Server was required.

Additional Information

moduleload statement
Specifies which database back-ends are loaded.
Depending on which database you are using, code a moduleload parameter for each.
The valid back-ends available are back_caacf2_utf, back_catss_utf, back_ldap, and back_cadb2_utf, back_cmgr_utf, and back_racf_utf.
This configuration option is global and
must 
be configured before any database sections.
Example: 
moduleload back_cmgr_utf.dll