SOA Suite 11.1.1.7 with IAM 11.1.2?

I know the installation guide specified SOA 11.1.1.6 with IAM 11.1.2, but is there an implied + where SOA 11.1.1.7 could be used instead?
Thanks!
mkc

Nope. You must use the versions listed in the installation guide. Just like with OIM R1, you had to use SOA 11.1.1.5
-Kevin

Similar Messages

AIA 2.4 installation on SOA suite 10.1.3.4 with Weblogic 9.2 MP3

Hi
I am trying to install AIA 2.4 on SOA suite 10.1.3.4 with Weblogic 9.2 MP3.
I could successfully install SOA suite 10.1.3.4 with Weblogic 9.2 MP3 and applied MLR # 9 Patch as well.
I am looking for document reference(step by step document) To install AIA 2.4 on weblogic.
When i used AIA 2.4 installer it was asking for OPMN port/OC4J instance name. Is there any other AIA 2.4 Installer for weblogic server?
Thanks

Of course, seeing 2.x I mistakenly thought PIPs as AIA Foundation Pack is now current version of 11gR1. Anybody wishing to install AIA Foundation Pack, especially with WLS should use 11gR1.
Can you elaborate on the reason you are electing to go with an older version of both AIA Foundtion Pack and SOA Suite?

SOA Suite 11.1.1.3 with WLS_1033 - Problem starting - vanishes away-no log

I just installed the latest version of SOA Suite 11.1.1.3 with WLS 1033 incl. RCU etc. on Windows XP SP2
when I do start the server (from the Windows Program shortcut or from the prompt) the admin server starts and the cmd window closes after about 30 lines of commands (which I cannot exactly see, as passing by too quick) and without giving more information...(;-(
When I try to stop the admin server, it is stating, that there is a lack of memory heap for the VM (I use SUN JDK 1.60_18)
Whereas I adjusted the memory in "setSOADomainEnv.cmd" like "set DEFAULT_MEM_ARGS=-Xms512m -Xmx512m" as in SOA Suite 11.1.1.2 and also 1024m will not help....
Any assistance to get my server running wud be appreciated !
TIA
Bernhard
From the command line window when tryiing to stop (whereas the server has not yet started) I only got:
USER_MEM_ARGS=-Xms512m -Xmx1024m -XX:PermSize=512m -XX:MaxPermSize=512m
JAVA_OPTIONS= -Xverify:none
** End SOA Specific environment setup for win.
** SOA specific environment is already set. Skipping ...
Stopping Weblogic Server...
Error occurred during initialization of VM
Could not reserve enough space for object heap
Could not create the Java virtual machine.
Done
Stopping Derby Server...
Edited by: BernhardFW on Jul 21, 2010 3:20 PM
after a fourth install I got it running now with JRockit (!!!) - which leads me to believe, there is a JDK Problem.....
Edited by: BernhardFW on Jul 22, 2010 10:04 AM

Bernard,
I had the same problem, I fixed it by cleaning up all my JDK's on my machine. I had some incomplete uninstalled older JDK's on my machine, which left some entries in the Windows Registry. I could see them in the 'Add or remove Programs' control panel, but could not uninstall them and got a Windows error message instead.
The exact steps to fix this are:
- uninstall all JDK's from the 'Add or remove Programs' control panel
- remove all remaining JDK files from the file system
- remove all JDK entries from the Windows Registry
- do a fresh JDK installation
For me, this fixed the problem

SOA suite 10.1.3.3 with OHS Apache 2.0 ... mod_oc4j errors

Hi all,
I have a SOA Suite 10.1.3.3 environment fronted by Apache 2.0.
Installed OHS 2.0 from the Companion CD in a new OHS ORACLE_HOME
Installed SOA Suite 10.1.3.3 in a new J2EE ORACLE_HOME
Can access the consoles ok (BPEL, ESB, etc ...).
Can access EM ok.
Can deploy BPEL processes OK.
However, deployment of ESBs fail.
The Apache 2.0 error_log has the following message:
[Thu Feb 28 10:08:08 2008] [debug] /ade/aime_asrc2_2/oracle/asg_apache/oc4j/src/oc4j_ajp13_worker.c(1288): mod_oc4j: AJP error talking to OC4J atsapdod03:12511: recv failed, 0
[Thu Feb 28 10:08:08 2008] [error] [client 10.38.75.180] mod_oc4j: request to OC4J atsapdod03:12511 failed: Connect failed
Looking at the oc4j-status page, the OC4J container running on atsapdod03:12511 is the container that holds the esb-dt application.
Has anyone out there got Apache 2.0 working with the SOA Suite?

Looks definitely to be an issue with OHS Apache 2.0.
* Shutdown OHS Apache 2.0
* Installed OHS 1.3 in a new ORACLE_HOME.
* Reconfigured OHS 1.3 to run on the same ports as OHS Apache 2.0
* Started OHS 1.3
* All works OK

SOA Suite 11g and its compatibility with Weblogic

Hi ,
I have two questions:
1. From where do I download the SOA Suite 11g --Link to the download?
2.If SOA suite 11g can be installed on weblogic. I understand that SOA suite 10.1.3.4 is compatible with weblogic 9.2 but need some inputs on the SOA Suite11g!
Cheers
Prabal

Prabal,
Did you get an answer or we have to wait for the official release till July-1-2009.
Thanks,
Rahul

Oracle SOA Suite 11g (BPEL Process) Dependency with Database

Folks,
Oracle SOA Suite 11g requires a relational DB like Oracle, SQL Server to maintain the Metadata for the SOA & Related Components.
Can you plz let me know with your experience - what should happen to a running BPEL Process if the database (SOAINFRA) is down? Being very specific -
1, Does/Should end-point become inaccessible? Or Does service remains accessible but throws service remote-fault execption?
2, What happens to a process which is in running state?
My experience in these scenarios is not encouraging; we have notices the following -- during the time when our SOAINFRA database is down, the in-process (running) instances are left in a running state. These instances do not complete or move forward even when the Database is back. These instances do not provide any information in the Enterprise Manager.
Also, if DB is down WSDL's are still accesssible, is this right way?
If this is how SOA does work then I would doubt for its merit……...your thought plz????
Thanks & Regards
Shyam Kumar

I am not posting here because I'm smart but because your questions look interesting.
during the time when our SOAINFRA database is down, the in-process (running) instances are left in a running stateYou know that BPEL is a state-full product and it needs database support for persisting the process of state so if database goes down it is an expected behavior that processes may stuck in the same state where they were when DB went down. I don't see anything wrong with it.
These instances do not complete or move forward even when the Database is back.Instances should auto/manually recoverable. If this is not the case then you may raise a SR with support.
These instances do not provide any information in the Enterprise Manager. What information you could not find? Can you be more clear on this?
Also, if DB is down WSDL's are still accesssible, is this right way?Yes, again it's expected because design time data also gets stored in DB only and hence if DB goes down, any design time data may not be accessible.
If this is how SOA does work then I would doubt for its merit……...your thought plz????Why so? Alternative of DB is physical memory and that I don't think is perfect for long running BPEL processes and their heavy design time data. Moreover, it will create problems in terms of auditing, support and maintenance. If your requirement is such that it does not need any long running BPEL processes and even auditing is not required and use case is simple routing and transformation with no DB dependency then you may go for OSB which is a stateless product. BPEL is generally used for long running processes and hence DB is the best option, in my opinion at least.
Regards,
Anuj

Installing AIA FP 2.4 on SOA Suite 10.1.3.4 with Weblogic 9.2 failed

Hi,
While Installing AIA FP 2.4 on Weblogic 9.2 using FPWLInstall.xml,
I got the following Error..
BUILD FAILED
D:\AIA_HOME\Infrastructure\install\wlscripts\FPWLInstall.xml:218: The following error occurred while executing this line:
D:\AIA_HOME\Infrastructure\install\wlscripts\FPWLInstall.xml:226: The following error occurred while executing this line:
D:\AIA_HOME\Infrastructure\install\wlscripts\FPWLDeployment.xml:17: The following error occurred while executing this line:
D:\AIA_HOME\Infrastructure\install\wlscripts\FPWLDeployment.xml:29: The following error occurred while executing this line:
D:\AIA_HOME\Infrastructure\install\wlscripts\FPWLErrorHandlingInstall.xml:140: The following error occurred while executing this line:
D:\AIA_HOME\Infrastructure\ErrorHandling\AIAReadJMSNotificationProcess\build.xml:209: A problem occured while connecting to server "localhost" using port "9700": bpel_aiareadjmsnotificationprocess_1.0.jar failed to deploy. Exception message is: Could not initialize activation agent.
An error occured while initializing an activation agent for process "AIAReadJMSNotificationProcess", revision "1.0".
Please ensure that the activation agents are configured correctly in the bpel deployment descriptor (bpel.xml).
oracle.tip.adapter.fw.agent.jca.JCAActivationAgent: ORABPEL-12517
AdapterFrameworkImpl::endpointActivation - Endpoint Activation Error.
The Resource Adapter was unable to activate the endpoint :{} due to the following reason: ORABPEL-12561
Unable to locate the JCA Resource Adapter via WSDL port element jca:address.
*The Adapter Framework is unable to startup the Resource Adapter specified in the WSDL jca:address element: {http://xmlns.oracle.com/pcbpel/wsdl/jca/}address: location='eis/Jms/AIA_ERROR_JMS'*
The reason for this is most likely that either
*1) the Resource Adapters RAR file has not been deployed successfully to the WebLogic J2EE Application server or*
*2) the JNDI location setting in the WebLogic JCA deployment descriptor has not been set to eis/Jms/AIA_ERROR_JMS. In the last case you might have to add a new 'connector-factory' entry (connection) to the deployment descriptor.*
Please correct this and then restart the BPEL/WebLogic Application Server
Please correct the reported issue and redeploy the BPEL process.
Please help.

pls see http://bit.ly/ozJqoz , in case you have missed some steps.

How to deal with any UDDI in SOA Suite 11g?

Hi folks,
I have spent quite some time trying to understand how Oracle is dealing with the UDDI aspects in the Soa Suite 11g.
Back to Oracle AS 10g, I remember, even though i had never used it, that the UDDI repository was a out of the box capability with a very nice Web UI to browse the services The Aqualogic Service Bus seems to have features to consume/publish web services in any UDDI, but no real embedded UDDI in its core.
Since 11g, obviously the way to go is to adopt Oracle Service Registry. There is a seamless integration with JDeveloper 11g (i.e create a UDDI connection to publish/consume/search web services).
My company is keen to go on a open source UDDI and I came to the conclusion that any of those (i.e jUDDIv3.02, OpenUDDI) are actually able to work properly with JDeveloper 11.1.1.2. I got XSD exception or other cabalistic errors that definitely show that JDeveloper 11g can only deal with Oracle Service Registry. I heard that the Soa Suite 11g could only deal with UDDI v2 and v3. CentraSite does fit those requirements but does not work too.
Why is that ? How can I set up my SOA initiative without having the choice on the UDDI ? Does this have changed since PS2 ? I have tried to look up on Metalink and I got a hit on jUDDI but it does clearly state that jUDDI works well now with JDeveloper.
Any answer on that would be highly appreciated.
Kind regards,

Hi,
DVM cache policy is lazy load. there is no option to preload the cache with server startup currently. However this would be affecting only the first request the susequent requests are serviced from cache.
HTH..
appologies for reaching on this late.
regards,
Jitendra

Business Rules Decision Service Error using SOA Suite with the WebLogic

Hi,
We are working with Oracle SOA Suite 10.1.3.4 on WebLogic 9.2. We have some decision services that work properly on Oracle SOA Suite 10.1.3.4 with Oracle Application Server. Following http://download.oracle.com/docs/cd/E12524_01/core.1013/e13058/weblogic.htm, we have made necesary changes and deployed bpel process and deployed manually Decision Services EAR Files on Weblogic.
When we invoke decision service from BPEL proccess next error appears, Could anybody help me to knows if this is a product installation/configuration problem or there is a failure on my ear rule file?
Any help would be appreciated. Regards,
<messages><input><dsIn><part xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" name="payload"><assertExecuteWatchStateful name="AsignarTaller" xmlns="http://www.oracle.com/PoC/ProcesoTest/AsignarTaller">
<configURL>http://devenv:9700/orabpel/default/modelo_proceso__test/1.0/decisionservices.decs</configURL>
<bpelInstance>
<processId xmlns="http://xmlns.oracle.com/bpel">modelo_proceso__test</processId>
<processVersion xmlns="http://xmlns.oracle.com/bpel">1.0</processVersion>
<domainId xmlns="http://xmlns.oracle.com/bpel">default</domainId>
<processURL xmlns="http://xmlns.oracle.com/bpel">http://devenv:9700/orabpel/default/modelo_proceso__test/1.0</processURL>
<instanceId xmlns="http://xmlns.oracle.com/bpel">80004</instanceId>
<conversationId xmlns="http://xmlns.oracle.com/bpel"/>
</bpelInstance>
<assertList>
<datosTaller xmlns="http://www.oracle.com/PoC/ReglaTalleres">
<provincia>1</provincia>
<nombreTaller/>
</datosTaller>
</assertList>
</assertExecuteWatchStateful>
</part></dsIn></input><fault><bindingFault xmlns="http://schemas.oracle.com/bpel/extension"><part name="code"><code>Server</code>
</part><part name="summary"><summary>[Server CodecHandler] Failed to encode Failed to encode message</summary>
</part><part name="detail"><detail><detail>
<bea_fault:stacktrace xmlns:bea_fault="http://www.bea.com/servers/wls70/webservice/fault/1.0.0" xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/">weblogic.wsee.codec.CodecException: Failed to encode message
     at weblogic.wsee.codec.soap11.SoapCodec.encode(SoapCodec.java:111)
     at weblogic.wsee.ws.dispatch.server.CodecHandler.encode(CodecHandler.java:103)
     at weblogic.wsee.ws.dispatch.server.CodecHandler.handleResponse(CodecHandler.java:50)
     at weblogic.wsee.handler.HandlerIterator.handleResponse(HandlerIterator.java:242)
     at weblogic.wsee.handler.HandlerIterator.handleResponse(HandlerIterator.java:226)
     at weblogic.wsee.ws.dispatch.server.ServerDispatcher.callHandleResponse(ServerDispatcher.java:142)
     at weblogic.wsee.ws.dispatch.server.ServerDispatcher.dispatch(ServerDispatcher.java:115)
     at weblogic.wsee.ws.WsSkel.invoke(WsSkel.java:80)
     at weblogic.wsee.server.servlet.SoapProcessor.handlePost(SoapProcessor.java:66)
     at weblogic.wsee.server.servlet.SoapProcessor.process(SoapProcessor.java:44)
     at weblogic.wsee.server.servlet.BaseWSServlet$AuthorizedInvoke.run(BaseWSServlet.java:181)
     at weblogic.wsee.server.servlet.BaseWSServlet.service(BaseWSServlet.java:92)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:856)
     at weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:227)
     at weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityHelper.java:125)
     at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:283)
     at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:175)
     at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:3244)
     at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
     at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121)
     at weblogic.servlet.internal.WebAppServletContext.securedExecute(WebAppServletContext.java:2010)
     at weblogic.servlet.internal.WebAppServletContext.execute(WebAppServletContext.java:1916)
     at weblogic.servlet.internal.ServletRequestImpl.run(ServletRequestImpl.java:1366)
     at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
     at weblogic.work.ExecuteThread.run(ExecuteThread.java:181)
Caused by: com.bea.xml.XmlException: object type unknown: class oracle.xml.parser.v2.XMLElement
     at weblogic.wsee.bind.types.SOAPElementTypeMapper.serialize(SOAPElementTypeMapper.java:94)
     at weblogic.wsee.bind.types.SOAPElementTypeMapper.serializeElement(SOAPElementTypeMapper.java:110)
     at weblogic.wsee.bind.types.TypeRegistry.serializeElement(TypeRegistry.java:161)
     at weblogic.wsee.bind.runtime.internal.BaseSerializerContext.serializeElement(BaseSerializerContext.java:123)
     at weblogic.wsee.codec.soap11.SoapEncoder.encodePart(SoapEncoder.java:272)
     at weblogic.wsee.codec.soap11.SoapEncoder.encodeReturn(SoapEncoder.java:188)
     at weblogic.wsee.codec.soap11.SoapEncoder.encodeParts(SoapEncoder.java:175)
     at weblogic.wsee.codec.soap11.SoapEncoder.encode(SoapEncoder.java:102)
     at weblogic.wsee.codec.soap11.SoapCodec.encode(SoapCodec.java:105)
     ... 24 more
Caused by: com.bea.xml.XmlException: object type unknown: class oracle.xml.parser.v2.XMLElement
     at weblogic.wsee.bind.types.SOAPElementTypeMapper.serialize(SOAPElementTypeMapper.java:94)
     at weblogic.wsee.bind.types.SOAPElementTypeMapper.serializeElement(SOAPElementTypeMapper.java:110)
     at weblogic.wsee.bind.types.TypeRegistry.serializeElement(TypeRegistry.java:161)
     at weblogic.wsee.bind.runtime.internal.BaseSerializerContext.serializeElement(BaseSerializerContext.java:123)
     at weblogic.wsee.codec.soap11.SoapEncoder.encodePart(SoapEncoder.java:272)
     at weblogic.wsee.codec.soap11.SoapEncoder.encodeReturn(SoapEncoder.java:188)
     at weblogic.wsee.codec.soap11.SoapEncoder.encodeParts(SoapEncoder.java:175)
     at weblogic.wsee.codec.soap11.SoapEncoder.encode(SoapEncoder.java:102)
     at weblogic.wsee.codec.soap11.SoapCodec.encode(SoapCodec.java:105)
     at weblogic.wsee.ws.dispatch.server.CodecHandler.encode(CodecHandler.java:103)
     at weblogic.wsee.ws.dispatch.server.CodecHandler.handleResponse(CodecHandler.java:50)
     at weblogic.wsee.handler.HandlerIterator.handleResponse(HandlerIterator.java:242)
     at weblogic.wsee.handler.HandlerIterator.handleResponse(HandlerIterator.java:226)
     at weblogic.wsee.ws.dispatch.server.ServerDispatcher.callHandleResponse(ServerDispatcher.java:142)
     at weblogic.wsee.ws.dispatch.server.ServerDispatcher.dispatch(ServerDispatcher.java:115)
     at weblogic.wsee.ws.WsSkel.invoke(WsSkel.java:80)
     at weblogic.wsee.server.servlet.SoapProcessor.handlePost(SoapProcessor.java:66)
     at weblogic.wsee.server.servlet.SoapProcessor.process(SoapProcessor.java:44)
     at weblogic.wsee.server.servlet.BaseWSServlet$AuthorizedInvoke.run(BaseWSServlet.java:181)
     at weblogic.wsee.server.servlet.BaseWSServlet.service(BaseWSServlet.java:92)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:856)
     at weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:227)
     at weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityHelper.java:125)
     at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:283)
     at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:175)
     at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:3244)
     at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
     at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121)
     at weblogic.servlet.internal.WebAppServletContext.securedExecute(WebAppServletContext.java:2010)
     at weblogic.servlet.internal.WebAppServletContext.execute(WebAppServletContext.java:1916)
     at weblogic.servlet.internal.ServletRequestImpl.run(ServletRequestImpl.java:1366)
     at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
     at weblogic.work.ExecuteThread.run(ExecuteThread.java:181)
</bea_fault:stacktrace>
</detail>
</detail>
</part></bindingFault></fault></messages>

Hi Boris,
Looks like you have not run the post upgrade script for 10.1.3.4.
You need to install SOA 10.1.3.4 Basic Installation. Then start following : http://download.oracle.com/docs/cd/E12524_01/core.1013/e13058/weblogic.htm#BHCIIBFB
You basically, first install 10.1.3.4 basic SOA install, Apply the Opatch 7337034 (HOTPLUG: SOASUITE 10.1.3.4 ON WEBLOGIC 9.2 - CHANGES FOR HOTPLUGGABILITY). Install WLS 9.2 MP3.
Now, Download the Oracle SOA Suite 10.1.3.4 WebLogic Server 9.2 : patch : 7490612.
Then , Modify the following mandatory installation properties in the Weblogic_SOA10134_Base\SOADomain.properties file as per the documentation above.
Cheers
Anirudh Pucha

Upgrade of SOA Suite 10.1.3.4 weblogic server

We have Oracle SOA Suite 10.1.3.4 with weblogic 9.2 as application server. Can we safely upgrade weblogic server to 10.3.2 without disturbing SOA Suite deployments. e.g. BPEL processes.
thanks

Hello Derek !
Let me clarify:
1. FP for SOA Suite on OC4J requires advance install of SOA Suite.
2. FP for SOA suite on WLS requires basic version of SOA Suite.
Though the SOA Install guide for WLS talks about explicitly http://download.oracle.com/docs/cd/E10291_01/doc.1013/e11848/weblogic.htm#BHCBEIBE
I agree that this information is not explicit enough in AIA Install guide, I will see if this can be included in existing 2.4 guide and a new version be uploaded to metalink. if not I will have this corrected for 2.5 guide.
and you are correct , MLR 7 is not certified on WLS, after MLR3, only MLR 8 is certified on WLS.
Thanks
-Teja

Installing SOA suite 10.1.3.4 on weblogic server 10g

Hi,
My client has weblogic server 10g and they want to link SOA suite 10.1.3.4 with it. I got hold an Oracle doc on installing SOA 10.1.3.4 on weblogic 9.2. The only difference is the patch no which is applied after installing 10.1.3.4 patch.
I am unsure if the patch p7337034_101340_GENERIC, which is meant for weblogic 9.2 is compatible with 10g.
If there is a separate patch for weblogic 10g please help me?
Thanks
Prabal

SOA Suite 10.1.3.4 is unfortunately not certified for WLS 10. The first release that will be certified is going to be 11g, but this will be 10.3.
If you want SOA Suite on WLS then you need to install on 9.2.
cheers
James

Configure OSB 11g to use the same domain as SOA Suite 11g

Hi,
A quick question on OSB Installation and extend the weblogic domain created for soa for OSB also. Please guide me what i am following is the correct path.
I followed the soa 11g and osb 11g installation doc from Eric Elzinga blog also checked oracle doc. Am quite confused about the directory structure to cofigure SOA Suite 11g and OSB 11g.
After SOA suite install , I Configure Oracle SOA Suite by following the below path
Run: middleware/wlserver_10.3/common/bin/config.exe (followed the blog ON OSB 11g Installation from Eric Elzinga).
I have seen another path to configure soa suite from oracle doc
SOA_ORACLE_HOME\common\bin\config.cmd
eg: E:\oraclehome\11g\middleware\Oracle_SOA1\common\bin\config.cmd
both directory str are correct?
After OSB installation , to configure OSB , I choose to reuse the SOA Suite domain to extend it with the Oracle Service Bus components. so in that case , is it the right directory structure I am following is
<Middleware_Home>\oracle_common\common\bin\config.bat.
eg: E:\oraclehome\11g\middleware\oracle_common\common\bin\config.bat
Thanks in advance
jk

Eventually you configure the weblogic domain always (either it is for SOA or OSB or BPM or all), so you should use middleware/wlserver_10.3/common/bin/config.exe
Regards,
Anuj

Problem - Create RESTFull Service Using SOA Suite

Hello folks, I am facing an issue while trying to create a simple REST WS with JDev and SOA Suite 11g. I have tried with JDev 11115, what I get from that is when I call the service endpoint I get a null pointer exception, just as described here:
http://biemond.blogspot.com/2010/05/http-binding-in-soa-suite-11g-ps2.html
I then tried to use JDev 11120 but the SOA Suite extension does not work with this version.
Any ideas on how to resolve the issue? Is there any bug fixes for JDev 11115?
Thank you in advance,
Andre

I am having the same issue. Any help is appreciated.

Soa suite on weblogic server 10.0??? URGENT!!!!!

hi,
we have a requirement to use ejb3.0 in our project. we are using soa suite on weblogic server 9.2. but weblogic 9.2 is not supporting ejb3.0 ( i guess). so we want to migrate weblogic server form 9.2 to 10.0. my doubt,is Oracle soa suite 10.1.3.3 is compatible with weblogic server 10.0??
otherwise any alternative??
please help me out.
Thanks in advance.

You are correct - SOA Suite 10.1.3.3 is not certified with WLS 10.x. We are currently in the process of certifying SOA Suite 10.1.3.4 with WLS 10.3.
Heidi.

INVOKING BPEL PROCESS PORTAL 10.1.4 + SOA SUITE 10.1.3.1

Hi,
Did anyone try to invoke BPEL Process / ESB service from portal 10.1.4 while using Soa Suite 10.1.3.1 with omniportlet? I tried that but when i point to WSDL it says that there are no methods in WSDL or that there is no endpoint. I dont believe any of these are true, cause i wrapped BPEL process in another BPEL Process and invocation was seamless.
thanks,
Chris.

Its not certified, you need to install on 9.2.
I believe this will be delivered in 10.1.3.5 which should be out before 1 June.
cheers
James

SOA Suite 11.1.1.7 with IAM 11.1.2?

Similar Messages

Maybe you are looking for