This topic lists the steps required to set up access to the administrative server that can be found on the LDAP server.
C:\Program Files\IBM\LDAP\bin>ibmslapd Server starting. Plugin of type EXTENDEDOP is successfully loaded from libevent.dll. Plugin of type EXTENDEDOP is successfully loaded from libtranext.dll. Plugin of type EXTENDEDOP is successfully loaded from libldaprepl.dll. Plugin of type PREOPERATION is successfully loaded from libDSP.dll. Plugin of type EXTENDEDOP is successfully loaded from libevent.dll. Plugin of type EXTENDEDOP is successfully loaded from libtranext.dll. Plugin of type AUDIT is successfully loaded from C:/Program Files/IBM/LDAP/bin/l ibldapaudit.dll. Plugin of type EXTENDEDOP is successfully loaded from libevent.dll. Plugin of type EXTENDEDOP is successfully loaded from libtranext.dll. Plugin of type DATABASE is successfully loaded from C:/Program Files/IBM/LDAP/bi n/libback-rdbm.dll. Plugin of type REPLICATION is successfully loaded from C:/Program Files/IBM/LDAP /bin/libldaprepl.dll. Plugin of type EXTENDEDOP is successfully loaded from libevent.dll. Plugin of type DATABASE is successfully loaded from C:/Program Files/IBM/LDAP/bi n/libback-config.dll. Error code -1 from odbc string:” SQLConnect “ SFSLDAP . SQL1063N DB2START processing was successful. Plugin of type EXTENDEDOP is successfully loaded from libloga.dll. Non-SSL port initialized to 389. IBM Directory (SSL), Version 5.1 Server started.
C:\Program Files\IBM\LDAP\appsrv\bin>startserver.bat server1 ADMU0116I: Tool information is being logged in file C:\Program Files\IBM\LDAP\appsrv\logs\server1\startServer.log ADMU3100I: Reading configuration for server: server1 ADMU3200I: Server launched. Waiting for initialization status. ADMU3000I: Server server1 open for e-business; process id is 1916
http://localhost: 9080/IDSWebApp/IDSjsp/Login.jsp
Parent topic: Configuring LDAP using IBM Directory Server Version 5.1
Previous topic: Configuring Directory Server for SAN File System