Monthly Archive: January 2014

Configure Apache Webserver to authenticate from LDAP Server

1. Connect to the LDAP Server from an LDAP Browser

ldap browser

ldap browser connected

2. Uncomment these two modules in httpd.conf

LoadModule ldap_module modules/
LoadModule authnz_ldap_module modules/

3. Add the following Location directive

<Location />

AuthType Basic
Require valid-user
AuthName   “Enter Your ldap Username/Password”
AuthBasicProvider   ldap
AuthzLDAPAuthoritative   off
AuthLDAPURL    ldap://localhost:444
AuthLDAPBindDN    “uid=faisal,ou=People, dc=bea,dc=com”
AuthLDAPBindPassword    faisal
ErrorDocument    401   “Please use your ldap username and password to login.”


4. Restart Apapche Webserver

5. Log in to the server with LDAP Credentials




login success

Starting a specific JBOSS server profile and a specific ip-address

 A. Starting a specific JBOSS server profile :

1. Navigate to the path …\jboss-eap-5.1\jboss-as\server

2. The server folder has different profile. Create a duplicate copy of the default folder and rename it to server1. We can  customize this profile and start it.

3. To start server1 , navigate to the path …\jboss-eap-5.1\jboss-as\bin\ and open the command prompt.

4. Enter the command  run -c server1 ( “-c” is used to choose the profile name)


Once, the command is executed the server1 profile starts


5. To check the console, go to http://localhost:8080/jmx-console


6. Enter the Username and Password (I have used my credentials to log in, we will cover how to manage user credentials password later in this article). The JMX Agent View console is displayed:


B. Starting a specific JBOSS server on a given IP-Address :

1. Repeat steps 1-3 in section A.

2. Enter the command  run -c server1 -b ip-address ( “-b” is used to run the server on the specific ip-address)

Installing JBoss EAP as a windows service

1. Copy …\jboss-ep-5.1\native\sbin to …\jboss-eap-5.1\jboss-as\bin

2.  Locate the cmd.exe file in the path  C:\Windows\System32\ and right click to Run as administrator.


The following command prompt is displayed:


3.  Navigate to the path  …\jboss-eap-5.1\jboss-as\bin\ in the command prompt and execute the command service.bat install


The service JBEAP5SVC -SERVER1 has been created.

4. We can start and stop the service from the Task Manager.



Managing Password in JBOSS EAP

1. Navigate to …\jboss-eap-5.1\jboss-as\server\server1\conf\props .

2.  Open the file and add roles as required.  I added the role saky , which I use to  login to jmx-console. Refer the sample file

# A sample file for use with the UsersRolesLoginModule


3. Similarly, Open the file and edit passwords for the users. 

# A sample file for use with the UsersRolesLoginModule

Important: jmx-console is mapped in login-config.xml  ( …\jboss-eap-5.1\jboss-as\server\server1\conf\ ).

<application-policy name=”jmx-console”>
<login-module code=””
<module-option name=”usersProperties”>props/</module-option>
<module-option name=”rolesProperties”>props/</module-option>

Note: Restart the server if any changes are made in any of these configuration settings

Starting the default JBOSS server

1. Navigate to the path …\jboss-eap-5.1\jboss-as\bin\ and open the command prompt.

2. Enter the command run.bat to start the JBOSS server


Once, the command is executed the  default profile for  JBOSS server starts



3. To check the console, go to http://localhost:8080/admin-console


4. Enter the Username and Password (I have used Admin credentials to log in, we will cover how to Managing Password article). The JBOSS Admin console is displayed:


NodeManager issues during oracle weblogic server environment setup

I/O error while reading domain directory: Domain directory ‘D:\bea\wlserver_10.3\common\nodemanager’ invalid (domain salt file not found

We need to to nmEnroll and restart the nodemanager to fix this error.

weblogic.nodemanager.common.ConfigException: Native version is enabled but node manager native library could not be loaded

You need to set the LD_LIBRARY_PATH for Solaris/Linux and SHLIB_PATH for HP-UX



Fatal error in node manager server
at weblogic.nodemanager.server.ServerManager.getStartCallbacks(
at weblogic.nodemanager.server.AbstractServerManager.initialize(
at weblogic.nodemanager.server.AbstractServerManager.(

This is a bug on WLS and there is a patch available for this.
Please contact Oracle Customer Support.