Unable To Pass Data From Bpel to Bam Due To "Failed for Negotiate, NTLM BAM domain" Error (Doc ID 796579.1)

Last updated on APRIL 28, 2009

Applies to:

Oracle Application Server Integration BAM - Version: 10.1.3.4
This problem can occur on any platform.

Symptoms

When attempting to send information from BPEL to BAM using sensors, no data is sent to BAM.
The following error occurs:

Domain.log

  <default.collaxa.cube.sensor> BAM exception: java.io.IOException message:
Authentication Failed for Negotiate, NTLM BAM domain: SOADOMAIN BAM user: Administrator BAM basic auth:
SOADOMAIN/Administrator BAM URL:
http://soatest:80/OracleBAMWS/Services/DataObject/DataObjectOperations.asmx
<WARN> <default.collaxa.cube.sensor> java.io.IOException: Authentication Failed for
Negotiate, NTLM
at
com.collaxa.cube.engine.sensor.sa.publisher.bam.BAMServerConnection.testConnection(BAMServerConnecti
on.java:279)
at
com.collaxa.cube.engine.sensor.sa.publisher.bam.BamEndpoint.testEndpoint(BamEndpoint.java:444)
at
com.collaxa.cube.engine.sensor.sa.publisher.bam.BamEndpoint.testConnection(BamEndpoint.java:373)
at
com.collaxa.cube.engine.sensor.sa.publisher.bam.BamEndpoint.pingBamAndFlushExceptionQueue(BamEndpoin
t.java:292)
at
com.collaxa.cube.engine.sensor.sa.publisher.bam.BamDataObjectMetadata.pingBamAndFlushExceptionQueue(
BamDataObjectMetadata.java:226)
at com.collaxa.cube.engine.sensor.sa.publisher.bam.BamJob.pingAction(BamJob.java:69)
at com.collaxa.cube.engine.sensor.sa.publisher.bam.BamJob.execute(BamJob.java:58)
at org.quartz.core.JobRunShell.run(JobRunShell.java:191)
at org.quartz.simpl.SimpleThreadPool$WorkerThread.run(SimpleThreadPool.java:516)

java.io.IOException: Authentication Failed for Negotiate, NTLM
at
com.collaxa.cube.engine.sensor.sa.publisher.bam.BAMServerConnection.testConnection(BAMServerConnecti
on.java:279)
at
com.collaxa.cube.engine.sensor.sa.publisher.bam.BamEndpoint.testEndpoint(BamEndpoint.java:444)
at
com.collaxa.cube.engine.sensor.sa.publisher.bam.BamEndpoint.testConnection(BamEndpoint.java:373)
at
com.collaxa.cube.engine.sensor.sa.publisher.bam.BamEndpoint.pingBamAndFlushExceptionQueue(BamEndpoin
t.java:292)
at
com.collaxa.cube.engine.sensor.sa.publisher.bam.BamDataObjectMetadata.pingBamAndFlushExceptionQueue(
BamDataObjectMetadata.java:226)
at com.collaxa.cube.engine.sensor.sa.publisher.bam.BamJob.pingAction(BamJob.java:69)
at com.collaxa.cube.engine.sensor.sa.publisher.bam.BamJob.execute(BamJob.java:58)
at org.quartz.core.JobRunShell.run(JobRunShell.java:191)
at org.quartz.simpl.SimpleThreadPool$WorkerThread.run(SimpleThreadPool.java:516)


-- Steps To Reproduce:
The issue can be reproduced at will with the following steps:
1) Create a simple Data object in BAM
2) Create  BPEL project and define some sensors to send information to the Data Object defined on Step1
3) Deploy the process to a 10.1.3.4 SOA server
4) Create a new instance of the bpel project from the bpel control page.
5) Check the soa server opmn log for error and verify if the data made it to BAM.

Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms