In SAP its Required to setup an LDAP server.
“The Lightweight Directory Access Protocol (LDAP) is a feature of Windows 2000 or higher
that allows important information within a corporate network to be stored centrally on a server.
The advantage of storing information centrally for the entire network is that you need only
maintain data once, so avoiding redundancy and inconsistency.” – From SAP
As you can see, we instead choose to use the Active Directory Service. Since we are explaining how to install on a single Virtual Machine for personal use, we do not need to concern ourselves with the LDAP server. (If you are interested in this goto R/3 System Information in Directory Services in SAP Service Marketplace service.sap.com/msplatforms – Microsoft – Windows Server)
Implications for Login
The SAPMSG.ini file is a configuration file to find SAP systems and their message servers from the directory.
MMC
This is the GUI for administering SAP. Events can be tracked in this interface.
The first step is to prepare the Active Directory so it can store SAP data. (as you can see this was done in the LDAP step above) You will see the MMC after you have completed the base installation of SAP.
This is how you start and stop the SAP system. Do this by selecting the SAP logo and performing a right mouse click. Select “Stop”. Notice the change in the SAP logo color.
Then start SAP by doing the same action, but selecting “Start.” The system will boot with SAP started, just as Oracle starts from system startup.
The Process List is very handy in MMC. Here it shows we have a problem connecting to the database.
After we reboot this issue is solved. However, we still have problems. We can view them by selecting the Syslog to see its messages. Errors have different categories and our serious errors have to do with the database, so the SAP database is still not setup correctly. This should not be a surprise as we do not have any data loaded into the system yet.
