FileAdapter Problem

Question

Hi,
I sucessfull deploy FileAdapter connector and File2StoredProcedure sample, but when I change domain from
'default' to 'test' FileAdapter stops to work. The log message is:
<2004-12-20 14:15:05,076> <INFO> <test.collaxa.cube.engine.deployment> <CubeProc
essFactory::generateProcessClass>
bpelc> validating "C:\orabpel\domains\test\tmp\.bpel_File2StoredProcedure_1.0.ja
r\File2StoredProcedure.bpel" ...
bpelc> build directory is C:\orabpel\domains\test\tmp\.bpel_File2StoredProcedure
_1.0.jar
Process "File2StoredProcedure" (revision "1.0") successfully compiled.
<2004-12-20 14:15:05,217> <INFO> <test.collaxa.cube.activation> <AdapterFramewor
k::Inbound> Locating Adapter Framework instance: ProcessConnect
<2004-12-20 14:15:05,248> <INFO> <test.collaxa.cube.activation> <AdapterFramewor
k::Inbound> Instantiating inbound part of Adapter Framework instance: ProcessCon
nect
<2004-12-20 14:15:05,264> <INFO> <test.collaxa.cube.activation> <AdapterFramewor
k::Inbound> JCAActivationAgent::initialize Initializing the JCA activation agent
, processId='File2StoredProcedure' activation properties={wsdlLocation=c:\Progra
~1\eclipse\workspace\File2StoredProcedure\FileInbound.wsdl, portType=FileInbound
_PortType}
<2004-12-20 14:15:05,264> <INFO> <test.collaxa.cube.activation> <AdapterFramewor
k::Inbound> JCAActivationAgent::activateInboundJcaEndpoints Initializing inbound
JCA endpoint: processId='File2StoredProcedure' WSDL location=c:\Progra~1\eclips
e\workspace\File2StoredProcedure\FileInbound.wsdl portType=FileInbound_PortType
operation=Receive activation properties={wsdlLocation=c:\Progra~1\eclipse\worksp
ace\File2StoredProcedure\FileInbound.wsdl, portType=FileInbound_PortType}
<2004-12-20 14:15:05,279> <INFO> <test.collaxa.cube.activation> <AdapterFramewor
k::Inbound> Adapter Framework instance: ProcessConnect - creating inbound listen
er for portType=FileInbound_PortType, operation=Receive, input Message Part=Inbo
undPayload
<2004-12-20 14:15:05,279> <INFO> <default.collaxa.cube.activation> <AdapterFrame
work::Inbound> Adapter Framework instance: ProcessConnect - endpointActivation f
or portType=FileInbound_PortType, operation=Receive
<2004-12-20 14:15:05,279> <INFO> <default.collaxa.cube.activation> <AdapterFrame
work::Inbound> Creating new instance of Resource Adapter oracle.tip.adapter.file
.FileResourceAdapter
<2004-12-20 14:15:05,295> <INFO> <default.collaxa.cube.activation> <AdapterFrame
work::Inbound> Adapter Framework instance: ProcessConnect - starting Resource Ad
apter oracle.tip.adapter.file.FileResourceAdapter
<2004-12-20 14:15:05,310> <INFO> <default.collaxa.cube.activation> <<Unnamed Ada
pter>::Inbound> AFTER STARTING FILE/FTP ADAPTER
[Error] FileInbound.wsdl:9:47: s4s-elt-schema-ns: The namespace of element 'defi
nitions' must be from the schema namespace, 'http://www.w3.org/2001/XMLSchema'.
[Error] FileInbound.wsdl:9:47: s4s-elt-invalid: Element 'definitions' is not a v
alid element in a schema document.
[Error] FileInbound.wsdl:9:47: src-include.1: The root element of document 'file
:/c:/Progra%7E1/eclipse/workspace/File2StoredProcedure/FileInbound.wsdl' has to
have the namespace name 'http://www.w3.org/2001/XMLSchema' and the local name 's
chema'.
<2004-12-20 14:15:05,467> <INFO> <default.collaxa.cube.activation> <File Adapter
::Inbound> ENDPOINT ACTIVATION CALLED IN FILE ADAPTER
04/12/20 14:15:05 Warning: Could not locate file pc.properties in classpath
<2004-12-20 14:15:05,514> <INFO> <default.collaxa.cube.activation> <File Adapter
::Inbound> AFTER ENDPOINT ACTIVATION IN FILE ADAPTER
<2004-12-20 14:15:05,514> <INFO> <default.collaxa.cube.activation> <AdapterFrame
work::Inbound> Adapter Framework instance: ProcessConnect - successfully complet
ed endpointActivation for portType=FileInbound_PortType, operation=Receive
<BaseCubeSessionBean::logError> Error while invoking bean "process manager": No
BPEL archive files.
The process domain cannot locate any BPEL archives for process "File2StoredProce
dure".
If you have deployed a process please check that it is located in the directory
"C:\orabpel\domains\default\deploy".
04/12/20 14:15:05 ORABPEL-05210
No BPEL archive files.
The process domain cannot locate any BPEL archives for process "File2StoredProce
dure".
If you have deployed a process please check that it is located in the directory
"C:\orabpel\domains\default\deploy".
The last line says that the process File2StoredProcedure must be located in ...\default\deploy directory.
I can't find the config file where I can change this.
When the File2StoredProcedure sample is in default domain, it works fine, but not in test nomain :-(.
Thanks
Martin

Answer 1

Hi Martin,
It looks like this problem is caused by a known restriction/issue which pertains only to the version you have (most likely 2.0.11). In the current Beta version (2.1) this issue has been addressed, as I just verified:
Your log shows:
<2004-12-20 14:15:05,279> <INFO> <test.collaxa.cube.activation> <AdapterFramework::Inbound> Adapter Framework instance: ProcessConnect - creating inbound listener for portType=FileInbound_PortType, operation=Receive, input Message Part=InboundPayload
The test I just ran showed:
<2004-12-20 19:25:37,765> <INFO> <test.collaxa.cube.activation> <AdapterFramework::Inbound> Adapter Framework instance: ProcessConnect - creating inbound listener for BPEL process=File2StoredProcedure, **domain=test**, portType=Read_ptt, operation=Read, input Message Part=InputParameters
As you can see my inbound JCA listener was created in the "test" domain. Also subsequent messages were correctly published to the BPEL Receive activity:
<2004-12-20 19:25:54,734> <INFO> <test.collaxa.cube.activation> <File Adapter::Inbound> Published message to Adapter Framework : { File=C:\OraHome_4\integration\bpm\samples\tutorials\122.DBAdapter\File2StoredProcedure\inputDir\payload.xml}
Until Oracle BPEL Process Manager 2.1 (or later) becomes available, there is unfortunately no other work-around but to stick with the "default" domain.
Thanks,
Bo