DP 8.1 LDAP Configuration (730 Views)
Reply
Respected Contributor
dcampregher
Posts: 216
Registered: ‎07-07-2011
Message 1 of 4 (730 Views)
Accepted Solution

DP 8.1 LDAP Configuration

HI,

 

When i try to initializing the LDAP Modules with the "jboss-cli.bat --file=ldapinit.cli", it doesn't generate the "standalone.xml" file, i searched with all directories within omniback but it aren't present.

The output otf the first command:

 

C:\Program Files\OmniBack\AppServer\bin>jboss-cli.bat --file=ldapinit.cli
{
    "outcome" => "success",
    "response-headers" => {
        "operation-requires-reload" => true,
        "process-state" => "reload-required"
    }
}
{
    "outcome" => "success",
    "response-headers" => {
        "operation-requires-reload" => true,
        "process-state" => "reload-required"
    }
}
Press any key to continue . . .

-----------
Please assign Kudos
HP Expert
Bob_Clark
Posts: 1,487
Registered: ‎08-14-2013
Message 2 of 4 (716 Views)

Re: DP 8.1 LDAP Configuration

The 'standalone.xml' file is supposed to be created in the folder

 

    Program Data -> Omniback -> Config -> Server -> AppServer

 

of the jboss application server, which, if I read the documentation correctly, is also the Cell Manager.  Just to be thorough, please check this folder, and make sure that the file is not there.  If you do find it, I'll send more Trouble-shooting steps, because Trouble-shooting involves editing the 'standalone.xml' file

 

Did you get any errors in the Application Eent log on the cell manager that correspond to this error?

 

What happens, when you see the message "Press any key to continue . . ." and you press any key?

 

I found nothing for any lab cases that may have reported this problem, so, if the file 'standalone.xml' file does not exist, you will need to open a case with the Response Center

 

Respected Contributor
dcampregher
Posts: 216
Registered: ‎07-07-2011
Message 3 of 4 (702 Views)

Re: DP 8.1 LDAP Configuration

HI Bob,

You are right, the standalone.xml file was generated in "Program Data -> Omniback -> Config -> Server -> AppServer" and i have been searched in "Program Files".

After change the "management interface" from 127.0.0.1 to 0.0.0 the service "Data Protector Appserver" doesn't initialize.

This is my test environment, any idea beacuse the service don't make up ?

 

Diogo

-----------
Please assign Kudos
HP Expert
Bob_Clark
Posts: 1,487
Registered: ‎08-14-2013
Message 4 of 4 (695 Views)

Re: DP 8.1 LDAP Configuration

You may want to make a copy of the 'standalone.xml' file before starting any of this, because all setting are going to need to be reset after tracing is done, and it may be easier to just replace the file with th eoriginal version

 

In the 'standalone.xml' file enable tracing:

 

change the logging level to "TRACE" for the periodic rotating file handler named "FILE":

 

<periodic-rotating-file-handler name="FILE">

<level name="TRACE"/>

 

 

Second, a category needs to be added to the logging subsystem for

org.jboss.security to be able to trace JBoss security issues:

 

<logger category="org.jboss.security">
<level name="TRACE"/>
</logger>

 

Third, the logging for DP specific logs should be set to trace level. This will enable trace level logs for the logs from

DpLoginModule

 

<size-rotating-file-handler name="DP_LOGGER" autoflush="true">
<level name="TRACE"/>
<formatter>
<pattern-formatter pattern="%d{HH:mm:ss,SSS} %-5p [%C{1}:%L:%t] %s%E%n"/>
</formatter>
<file relative-to="jboss.server.log.dir" path="DPServer.log"/>
<rotate-size value="10M"/>
<max-backup-index value="5"/>
<append value="true"/>
</size-rotating-file-handler>

 

Fourth, a category needs to be added to the logging subsystem for

com.hp.im to be able to trace DpLoginModule issues:

 

HP Data Protector 8.10 Update Training–LDAPIntegration and Certificates

<levelname="TRACE"/><formatter><pattern-formatterpattern="%d{HH:mm:ss,SSS}%-5p

[%C{1}:%L:%t]%s%E%n"/></formatter><filerelative-to="jboss.server.log.dir"path="DPServer.log"/><rotate-sizevalue="10M"/><max-backup-indexvalue="5"/><appendvalue="true"/>

</size-rotating-file-handler>

 

Fourth, a category needs to be added to the logging subsystem for

com.hp.imtobe able to trace DpLoginModuleissues:

<loggercategory="com.hp.im"><levelname="TRACE"/></logger>

 

Save the 'standalone.xml' file.  The log file traces will be written to is:

 

  Program Data -> Omniback -> Config -> log -> AppServer -> server.log

 

 

A successful login should look like this:

TRACE [org.jboss.security] (http--0.0.0.0-7116-11) PBOX000220: Logging into LDAP server with env (…)
TRACE [org.jboss.security] (http--0.0.0.0-7116-11) PBOX000268: Assigning user to role (…)
TRACE [org.jboss.security] (http--0.0.0.0-7116-11) PBOX000241: End login method, isValid: true
TRACE [org.jboss.security] (http--0.0.0.0-7116-11) PBOX000236: Begin initialize method
TRACE [org.jboss.security] (http--0.0.0.0-7116-11) PBOX000240: Begin login method
TRACE [org.jboss.security] (http--0.0.0.0-7116-11) PBOX000242: Begin commit method, overall result: true
TRACE [org.jboss.security] (http--0.0.0.0-7116-11) PBOX000242: Begin commit method, overall result: true

 

If it shows anything different, and I am sure that it will, you will need to open a case with the response center, and it will probably need to be elevated to Engineering. It is just that I am not sure if anyone there would know how to implement tracing.  You should probably keep a copy of your edited 'standalone.xml' file also in case they want you to do additional tracing

 

If you want me to look at your 'server.log' file, I certainly will to see if what you have is a know problem, just send it as an attachment to this forum thread

The opinions expressed above are the personal opinions of the authors, not of HP. By using this site, you accept the Terms of Use and Rules of Participation.