[peacefuleye]

Hi Chris,

I believe you have been through a successful integration between OTM and Oracle Purchasing before, could you please help me out on my case.

I'm integrating otm with oracle purchasing via BPEL currently.
OTM - 5.5.3
EBS - 11.5.10.2
BPEL- 10.2.0.2

I've applied ebs patch 5234512 per metalink note 370743.1, then I tried to deply bpel process bpel_PoSendPoToOtm, but the files PoSendPoToOtmBuild.xml and PoUpdateBpel.class can't be found under $JAVA_TOP/oracle/apps/po/bpel/util directory.

Even I can't see $JAVA_TOP/oracle/apps/po/bpel sub directory exsiting.

Have you met this before or is there any work around for this?

Thanks,
Alex

[chrisplough]

I haven't run into this issue before - as the required jars always ended up in $PO_TOP/bpel/jar/bpel_PoSendPoToOtm_1_0.jar. I hate to say this, but I'd re-apply the patch to ensure it went on correctly. If the problem persists, then you'll have to open an SR with Oracle.

Please keep us updated as to the progress.

Also, as a note - the version of BPEL recommended (and supported) for EBS / OTM integration has changed as is now 10.1.3.3. I'd recommend making this change now, rather than later in the project to save time.

--Chris

[peacefuleye]

Chris,

Thanks for your update. I've tried applying that patch again, but it did not make sense. Actually $PO_TOP/bpel/jar/bpel_PoSendPoToOtm_1_0.jar was there.

Coz PoSendPoToOtmBuild.xml and PoUpdateBpel.class can't be found so that I'm not able to deply this bpel process by obant.sh as instructed by oracle note.

Chris, is there any other way which can deploy this process manually?

Thanks,
Alex

[chrisplough]

Alex,

Hmm - that is strange. Well, I'd definitely open an SR with Oracle to get the issue formally resolved.

In the meantime, you should be able to simply extract the bpel_PoSendPoToOtm_1_0.jar file and then edit the BPEL configuration files (bpel.xml and others) to match your server's configuration (such as the OTM URI, DbAdapter and AqAdapter connection strings, etc), then package it back up and deploy it to your BPEL server.

To repackage the jar, you'd use a command like:

jar c0mvf ./META-INF/MANIFEST.MF ../ 
bpel_PoSendPoToOtm_1_0.jar *

I'm sure you can accomplish all of this via Oracle's JDeveloper, though I tend to work directly with the xml files.

--Chris

[peacefuleye]

Hi Chris,

Do you have any guide with how to change configuration files and what settings needs to be changed in these files?

Regards,
Alex

[chrisplough]

Alex,

I don't believe a guide is available, but here's the files that I've had to modify in the past with these flows:

• GLogXML.wsdl - the URI of your OTM instance to post integration to
• PoSendPoToOtm.wsdl - modify the partnerLinks to include the appropriate DB connection strings

I don't have the jar file in front of me (doing this from memory) - so this may be a bit rusty.

--Chris

[peacefuleye]

Hi Chris,

Oracle Support has provided the official action plan for this issue.

Patch 6489720 have to be applied after patch 5234512, and then PoSendPoToOtm process can be deployed as per metalink notes.

Thanks,
Alex