OSB and SOA Suite in the Java Cloud

Hi All -- the question is rather to a technical support personnel of the Oracle Cloud,
Is it possible to deploy and run the OSB and SOA Suite applications on the Oracle Java Cloud? To be more precise:
1. Is the WL server in the cloud configured to contain the Oracle Soa Suite?
2. Is the WL server in the cloud configured to contain the Oracle Service Bus?
If not: would it be possible to configure the Cloud WL domains the way that these are supported?
What we need are two servers (or two clusters): a SOA Suite application runs on one, while the OSB application runs on the other.
Thanks for help.

Hi Chris,
Oracle's statement of direction that you can find at
http://www.oracle.com/technology/products/integration/service-bus/docs/Oracle-Service-Bus-SOD.pdf
there will be convergence of the 2 products that basically address 2 different use cases (see Statement of Direction).
In my opinion new tools will be added to Jdeveloper to develop and deploy on Oracle Service Bus (OSB). In present OSB version, OSB tools are not part of Jdeveloper and transformations use XQuery instead of XSLT (as for Oracle ESB).
Hope this help you a little bit.
Regards,
Jean-Pierre

Similar Messages

OSB and SOA Suite on same home

Hi,
Which version of Oracle Service Bus can be installed on existing middleware home?
The target platform is - Oracle SOA Suite + Oracle service Bus. My assumption is it should be possible to "share" same m/w home (WLS10.3.5) between SOA Suite and OSB.
I am using SOA 11g (11.1.1.5.0) and WLS10.3.5
Please suggest.
regards,
Anand

Hi Chris,
Oracle's statement of direction that you can find at
http://www.oracle.com/technology/products/integration/service-bus/docs/Oracle-Service-Bus-SOD.pdf
there will be convergence of the 2 products that basically address 2 different use cases (see Statement of Direction).
In my opinion new tools will be added to Jdeveloper to develop and deploy on Oracle Service Bus (OSB). In present OSB version, OSB tools are not part of Jdeveloper and transformations use XQuery instead of XSLT (as for Oracle ESB).
Hope this help you a little bit.
Regards,
Jean-Pierre

OSB and SOA Suite VISIO Stencils

I am putting together some stencils to model my OSB / SOA Suite solution....
This one is REALLY cool, it contains very specific component icons, although I wish it contained more JEE specific terminology
http://www.soapatterns.com/SOA_Visio_Stencil.zip
This one is very abstract, anyway a few components can be really useful:
http://www.eaipatterns.com/download/EIP_Visio_stencil.zip
I am also experimenting externalizing the shapes data into an Excel sheet, and linking to the shapes.
As far as possible I would like to keep a strict inventory of all the artifacts created in OSB/SOA Suite, and keep them in sync with the documentation.
I wonder what your experience is, and if you have other tools to recommend?

Hi Chris,
Oracle's statement of direction that you can find at
http://www.oracle.com/technology/products/integration/service-bus/docs/Oracle-Service-Bus-SOD.pdf
there will be convergence of the 2 products that basically address 2 different use cases (see Statement of Direction).
In my opinion new tools will be added to Jdeveloper to develop and deploy on Oracle Service Bus (OSB). In present OSB version, OSB tools are not part of Jdeveloper and transformations use XQuery instead of XSLT (as for Oracle ESB).
Hope this help you a little bit.
Regards,
Jean-Pierre

OSB and SOA Suite 11.1.1.7 new features?

Hi,
I could not find the information about any new features in Oracle Service Bus and Oracle SOA Suite 11.1.1.7 release. (I know about the Adaptive case management in BPM 11.1.1.7)
Anyone has a link for that?
And if any one needs, here is the link for the resolved and known issues for this release: http://www.oracle.com/technetwork/middleware/docs/aiasoarelnotesps6-1866030.html#servbus
Thanks and Regards,
Abhishek

Oracle SOA Suite PS6 (11.1.1.7.0) is available now
Regards,
Anuj

Running OSB and SOA Suite as Windows Services? Node Manager

Hi,
Based on our current hardware configuration, we need to deploy our SOA Managed Server and Admin Server on the same machine as our OSB. Currently for development we just start the servers using the start scripts and keep a window open for them (3 of them: 1 - admin, 1 - soa_server1, and 1 - OSB.) We want to be able to run these as services and allow the admins to log out of the box. It seems like the Node Manager would allow us to do that but can we configure our Windows server to have a Node Manager running for the OSB and another for the SOA stuff on the same box? Do we even need to do that? Can we have a single Node Manager manage all three on port 5556?
I hope this makes sense. Thanks in advance for any quick responses.
Jeremy

Definitely you can (should) have a single node manager. You may refer below links -
http://blogs.oracle.com/jamesbayer/2010/01/weblogic_nodemanager_quick_sta.html
WLS 10.3.2 Adminserver startup failed when trying to run as Windows Service
Regards,
Anuj

OSB to SOA suite package not forming correctly

Setup is as follows:
AIX 5.3 on the box, 10 gigs ram, installation of the latest releases of OSB and SOA suite on top of weblogic. I've built out a couple of simple database queries in BPEL based off wsdls, dropped them on to the SOA suite server, used EM to open a test console and plugged in some search data. Search returns successfully.
I then open up OSB's console, create a business service to the endpoint on the soa server, and a proxy based off the same wsdl used in the BPEL construction which I then route to the business service. Both service and proxy are made with basic http for the protocol (not sure how to use the sb protocol, and not sure if that will fix the problem). Load the test console on the proxy service, which displays an xml form similar to what is used in the SOA suite. Fill out the same information, but the invoke returns BEA-380000. Following the invocation trace in OSB everything looks good in terms of package content.
Wondering if it might simply be a problem with how the OSB interprets XML from a wsdl, I piped the XML from the SOA suite into the OSB's xml field, but to no luck, same error. After some more testing and frustration,I put the SOA suite XML straight in to the form field in the OSB test console, and it worked. However, the package itself seems oddly formed, consisting of:
<soapenv:Envelope      xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/">
     <soap:Header      xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/">
     </soap:Header>
     <soapenv:Body>
     <soap:Envelope      xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/">
     <soap:Header/>
Which I've been told is basically double wrapping the package, which shouldn't work, and more importantly wont be generated when someone uses say SOAPUI to access our service on the OSB.
Now, on the SOA suite side of things. In EM console, I navigate to my BPEL process and can see the faults caused by the OSB. The same faults are also generated when binding to the OSB's endpoint with SOAPUI, but not when going directly to the SOA suite's endpoint. The error is the following:
oracle.j2ee.ws.saaj.soap.SOAPVersionMismatchException: Mime Header Content-Type: text/xml requires SOAP envelope namespace: http://schemas.xmlsoap.org/soap/envelope/: Mime Header Content-Type: text/xml requires SOAP envelope namespace: http://schemas.xmlsoap.org/soap/envelope/
And the payload sent shows as empty.
So to my best uneducated guess, it looks like the OSB wraps the payload in an envelope, and then unwraps it before handing it to the SOA suite, which expects the payload to be wrapped. Sadly, I'm still pretty new to the wsdl/webservice/oracle world, so I'm not even sure if that's an accurate representation. Any insight on what might be happening or how to get OSB to talk with SOA suite correctly would be greatly appreciated. Included below are the XML payloads I've used (minus a bit for confidentiality reasons). Apologies if the formatting doesn't work so nice for it.
OSB Generated (fails):
SOAP Header:
<soap:Header xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/">
</soap:Header>
Body:
<ns2:SyncEmployeeIDRequest xmlns:ns="removed" xmlns:ns1="removed" xmlns:ns2="removed">

<ns:PersonIdentificationAssertion>

<ns1:PersonBirthDate>
<ns1:Date>2008-09-28</ns1:Date>
</ns1:PersonBirthDate>

<ns1:PersonGivenName>string</ns1:PersonGivenName>
<ns1:PersonSurName>string</ns1:PersonSurName>
</ns:PersonIdentificationAssertion>
<ns1:DepartmentIDText>string</ns1:DepartmentIDText>
</ns2:SyncEmployeeIDRequest>
SOA Generated(works if plugged into OSB form field)
SOAP Header:
<soap:Header xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/">
</soap:Header>
<soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/">
     <soap:Header></soap:Header>
     <soap:Body xmlns:ns1="removed">
          <ns1:SyncEmployeeIDRequest xmlns:ns2="removed">
               <ns2:PersonIdentificationAssertion xmlns:ns3="removed">
                    <ns3:PersonBirthDate>
                         <ns3:Date>2008-09-28</ns3:Date>
</ns3:PersonBirthDate>
                    <ns3:PersonGivenName>string</ns3:PersonGivenName>
                    <ns3:PersonSurName>string</ns3:PersonSurName>
</ns2:PersonIdentificationAssertion>
</ns1:SyncEmployeeIDRequest>
</soap:Body>
</soap:Envelope>
Working Request Document in OSB:
<soapenv:Envelope      xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/">
     <soap:Header      xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/">
     </soap:Header>
     <soapenv:Body>
     <soap:Envelope      xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/">
     <soap:Header/>
     <soap:Body      xmlns:ns1="removed">
     <ns1:SyncEmployeeIDRequest      xmlns:ns2="removed">
     <ns2:PersonIdentificationAssertion      xmlns:ns3="removed">
     <ns3:PersonBirthDate>
     <ns3:Date>2008-09-28</ns3:Date>
     </ns3:PersonBirthDate>
     <ns3:PersonGivenName/>
     <ns3:PersonSurName>ALastName</ns3:PersonSurName>
     </ns2:PersonIdentificationAssertion>
     </ns1:SyncEmployeeIDRequest>
     </soap:Body>
     </soap:Envelope>
     </soapenv:Body>
     </soapenv:Envelope>
If I can provide anymore information that will help shed light on this issue please let me know.
Thank you for your time.
~Nick

Problem solved. When I originally created my business service inside of OSB, I created it based off an endpoint provided by the SOA server. Instead, I went and did a mass import from a url, pointed it at the SOA server wsdl, and then built the web service off of that wsdl resource in the OSB. Now it works like a charm.

OSB vs SOA suite

What is difference and relationship between OSB and SOA suite?
I see much much overlap between the two.
1.DB adapter, mq adapter, file adapter, app adapter,etc, exist in oracle service bus 10.3.1.Also SOA suite 11g has all theses components.
2.OSB is a WL domain in running time, SOA suite is also a WL domain in running time.
The difference is OSB does not support BPEL but SOA suite does.
Seems most of things done by OSB can also been done by SOA suite.
In what scenario we should use OSB and in what scenario we should use SOA suite instead?
Can someone give some helps on this?
Thanks
Edited by: user11997125 on May 20, 2010 2:28 AM
Edited by: user11997125 on May 20, 2010 2:29 AM

OSB is like the name says a 'Service Bus' and the soa suite is a suite of components which can be used to create a service oriented architecture. In this suite there isn't and service bus available for you.
So both products complement each other.
It's true most actions can be done in both the products/suites, but you should see them both in 1 total solution. After that decide what you design in the osb and what you design in the soa suite components.
if you check wikipedia for the definition of a service bus, you will see what the strengths are (or should be), some line virtualization/transformation/routing/etc.
from my point of view i would say, you create your interface on the service bus, keep the flows in the service bus lightweigh, and route to the 'real' services. These could be modelled in the soa suite components, and in there do the business logic

SOA Suite 10g and SOA Suite 11g? what are the major changes in these two?

Hi Experts,
I am keen in knowing about Soa Suite 11g. SOA Suite 10g and SOA Suite 11g, BPEL changes? what are the major changes in these two product/tool wise? Is now OSB is part of Soa Suite 11g? it would be helpful for us to know what are the major changes and updates or modifications came in 11g.
Please share this valuable information.
Is there still any version is in progress from Oracle, which is yet to be officially launched from oracle?

what are the major changes in these two product/tool wise? Few major changes to enlist are that SOA suite 10g was using Oracle Application Server (OC4J) however 11g is on Weblogic and 11g is based on SCA. B2B is now part of SOA suite itself and OSB can share a domain with SOA. You may refer below link to know few more -
http://blogs.oracle.com/soabpm/2010/03/11gr1_patchset_2_111130_soa_fe.html
Is now OSB is part of Soa Suite 11g? OSB has a separate installer but can share a domain with SOA and SOA-direct binding is also supported now. Refer below link to know more about new features in OSB 11g -
http://download.oracle.com/docs/cd/E14571_01/relnotes.1111/e10132/osb.htm#CJACHEHJ
Is there still any version is in progress from Oracle, which is yet to be officially launched from oracle?No major release is planned. Patches for 11g R1 may come.
Regards,
Anuj

How to configure osb and soa in single domain

Hi all,
hope all are fine.
sorry if this question is already posted.
I installed wls 10.3.6 and osb 11.1.1.6 & SOA 11.1.1.6 and domain cofiguration also successful.
in domain cofiguration i selected both osb and soa.
all (wls,osb,soa ) servers are up but soa_infra was down. I am unable to see soa folder in em.
where is the problem please provide solution for this...
thanks in advance.
Thanks
Mohan

Hi Harsh,
I tried with(developer template) that but again soa_infra was down. i am getting user messaging services.
admin server logs are
oracle.mds.lcm.exception.MDSLCMException: MDS-01330: unable to load MDS configuration document
MDS-01329: unable to load element "persistence-config"
MDS-01370: MetadataStore configuration for metadata-store-usage "soa-infra-store" is invalid.
ORA-04063: package body "DEV_MDS.MDS_INTERNAL_SHREDDED" has errors
ORA-06508: PL/SQL: could not find program unit being called: "DEV_MDS.MDS_INTERNAL_SHREDDED"
ORA-06512: at line 1
     at oracle.mds.internal.lcm.deploy.DeployManager.deploy(DeployManager.java:733)
     at oracle.mds.internal.lcm.deploy.DeployManager.startDeployment(DeployManager.java:204)
     at oracle.mds.internal.lcm.MDSLifecycleListenerImpl.start(MDSLifecycleListenerImpl.java:215)
     at oracle.mds.lcm.weblogic.WLLifecycleListener.preStart(WLLifecycleListener.java:77)
     at weblogic.application.internal.flow.BaseLifecycleFlow$PreStartAction.run(BaseLifecycleFlow.java:282)
     at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
     at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:120)
     at weblogic.application.internal.flow.BaseLifecycleFlow$LifecycleListenerAction.invoke(BaseLifecycleFlow.java:199)
     at weblogic.application.internal.flow.BaseLifecycleFlow.preStart(BaseLifecycleFlow.java:62)
     at weblogic.application.internal.flow.HeadLifecycleFlow.prepare(HeadLifecycleFlow.java:283)
     at weblogic.application.internal.BaseDeployment$1.next(BaseDeployment.java:648)
     at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
     at weblogic.application.internal.BaseDeployment.prepare(BaseDeployment.java:191)
     at weblogic.application.internal.EarDeployment.prepare(EarDeployment.java:59)
     at weblogic.application.internal.DeploymentStateChecker.prepare(DeploymentStateChecker.java:154)
     at weblogic.deploy.internal.targetserver.AppContainerInvoker.prepare(AppContainerInvoker.java:60)
     at weblogic.deploy.internal.targetserver.AppDeployment.prepare(AppDeployment.java:144)
     at weblogic.management.deploy.internal.DeploymentAdapter$1.doPrepare(DeploymentAdapter.java:39)
     at weblogic.management.deploy.internal.DeploymentAdapter.prepare(DeploymentAdapter.java:191)
     at weblogic.management.deploy.internal.AppTransition$1.transitionApp(AppTransition.java:21)
     at weblogic.management.deploy.internal.ConfiguredDeployments.transitionApps(ConfiguredDeployments.java:240)
     at weblogic.management.deploy.internal.ConfiguredDeployments.prepare(ConfiguredDeployments.java:165)
     at weblogic.management.deploy.internal.ConfiguredDeployments.deploy(ConfiguredDeployments.java:122)
     at weblogic.management.deploy.internal.DeploymentServerService.resume(DeploymentServerService.java:180)
     at weblogic.management.deploy.internal.DeploymentServerService.start(DeploymentServerService.java:96)
     at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
     at weblogic.work.ExecuteThread.execute(ExecuteThread.java:256)
     at weblogic.work.ExecuteThread.run(ExecuteThread.java:221)
Caused by: oracle.mds.config.MDSConfigurationException: MDS-01330: unable to load MDS configuration document
MDS-01329: unable to load element "persistence-config"
MDS-01370: MetadataStore configuration for metadata-store-usage "soa-infra-store" is invalid.
ORA-04063: package body "DEV_MDS.MDS_INTERNAL_SHREDDED" has errors
ORA-06508: PL/SQL: could not find program unit being called: "DEV_MDS.MDS_INTERNAL_SHREDDED"
ORA-06512: at line 1
     at oracle.mds.config.PConfig.loadFromBean(PConfig.java:959)
     at oracle.mds.config.PConfig.<init>(PConfig.java:758)
     at oracle.mds.config.MDSConfig.loadFromBean(MDSConfig.java:787)
     at oracle.mds.config.MDSConfig.loadFromElement(MDSConfig.java:848)
     at oracle.mds.config.MDSConfig.<init>(MDSConfig.java:491)
     at oracle.mds.config.MDSConfig.<init>(MDSConfig.java:438)
     at oracle.mds.internal.lcm.deploy.DeployManager.deploy(DeployManager.java:516)
     ... 27 more
Caused by: oracle.mds.exception.MDSExceptionList: MDS-01329: unable to load element "persistence-config"
MDS-01370: MetadataStore configuration for metadata-store-usage "soa-infra-store" is invalid.
ORA-04063: package body "DEV_MDS.MDS_INTERNAL_SHREDDED" has errors
ORA-06508: PL/SQL: could not find program unit being called: "DEV_MDS.MDS_INTERNAL_SHREDDED"
ORA-06512: at line 1
     at oracle.mds.config.PConfig.loadFromBean(PConfig.java:953)
     ... 33 more
I installed rcu correctly and db is up and i installed following combination
oepe-wls-indigo-installer-11.1.1.8.0.201110211138-10.3.6-win32
ofm_rcu_win_11.1.1.6.0_disk1_1of1
ofm_osb_generic_11.1.1.6.0_disk1_1of1
ofm_soa_generic_11.1.1.6.0_disk1_1of2
is there any mismatch combination.
Thanks
Mohan
Edited by: Mohan SOA on Sep 12, 2012 12:39 AM

OSB to SOA Suite communication

Hi,
We have an OSB cluster and SOA Suite cluster, spread over multiple servers (either physical or virtual) where each OSB managed server is on the same underlying O/S server as a corresponding SOA Suite managed server. A hardware load balancer will be used to expose an endpoint to service consumers. The load balancer will then distribute requests to either of the OSB managed servers.
My question is should the communication between the OSB managed servers be load balanced (and distrubuted) to the SOA Suite managed servers or should each OSB managed server speak locally to the corresponding SOA Suite managed server ?
My concern is that load balancing to SOA Suite introduces complexity without solving a resiliency problem (assuming a config over 4+ O/S servers), whereas local and direct communication keeps it simple in terms of logfile traceability and optimal performance (i.e. not going out on the netowrk again). I can see that in the event of a SOA Suite managed server going down or failing, you have to have a protective measure to ensure that requests to it's parent OSB managed server are stopped. This would need to be implemented at the OSB load balancer level.
I'm interested to understand what other people have done in this situation or if I'm missing some insight that would influence wither way.
TIA

user4709830 wrote:
My concern is that load balancing to SOA Suite introduces complexity without solving a resiliency problem (assuming a config over 4+ O/S servers), whereas local and direct communication keeps it simple in terms of logfile traceability and optimal performance (i.e. not going out on the netowrk again).This looks interesting... Assuming OSB and SOA servers are always in pairs hosted in the same machine, there's a high probability that if one is down, both will be down... Makes sense...
I can see that in the event of a SOA Suite managed server going down or failing, you have to have a protective measure to ensure that requests to it's parent OSB managed server are stopped. This would need to be implemented at the OSB load balancer level.Well, try to go around in the event of the half break, i.e. OSB up and SOA down, will be complex... I think here is a matter of assess the risk of that happening, the impacts and the effort needed to mitigate the impact versus the advantages you mentioned (logfile traceability and optimal performance)... How good are those advantages and would they really pay the effort/risk?
Hope this helps...
Cheers,
Vlad

Upgrade Weblogic10.3.3 and SOA Suite 11.1.1.3.0

Upgrade Weblogic10.3.3 and SOA Suite 11.1.1.3.0
We would like to upgrade Weblogic10.3.3 and SOA Suite 11.1.1.3.0 and have few questions related with upgrade.
Q-1 Should we upgrade to latest weblogic version WebLogic Server 10.3.6 ?
Q-2 Do we need to upgrade SOA Suite 11.1.1.6.0 compatible with WebLogic Server 10.3.6 ?
Q-3 Do we have step by step process for migration ?
Q-4 Do we need to create new schema for latest version of SOA Suite 11.1.1.6.0 ?
Q-5 What is the process to copy the existing data from database schema from SOA Suite 11.1.1.3.0 version to new SOA Suite 11.1.1.6.0

Hi,
i upgraded the SOA Suite from 11.1.1.4.to 11.1.1.7.
Q-1 Should we upgrade to latest weblogic version WebLogic Server 10.3.6 ?
Yes : aktually 10.3.6.0.9
Q-2 Do we need to upgrade SOA Suite 11.1.1.6.0 compatible with WebLogic Server 10.3.6 ?
Yes. Why 11.1.1.6, i would upgrade to the latest version 11.1.1.7
Q-3 Do we have step by step process for migration ?
Yes. You can check the MOS Note: https://support.oracle.com/epmos/faces/DocContentDisplay?id=1349156.1
Q-4 Do we need to create new schema for latest version of SOA Suite 11.1.1.6.0 ?
Not necessary. But you may test your upgrade. We upgraded out of the place. By Inplace Upgradeyou may have backup for the fallback.
Q-5 What is the process to copy the existing data from database schema from SOA Suite 11.1.1.3.0 version to new SOA Suite 11.1.1.6.0
Check the MOS Note above and Oracle Dokument Oracle Fusion Middleware Online Documentation Library

JMS Adapter Tuning in Oracle 10G SOA suite - Fixing the Errors

Hi All,
We are getting an error in Production environment while a BPEL process producing (enqueue) a message to a JMS queue by using JMS adapter. (partener link)
The error is as follows.
Adapter Framework unable to create outbound JCA connection.
file:/sw/appnew/product/SOA/10.1.3/bpel/domains/default/tmp/.bpel_CurrenListJMSProducer_1.0_4ec528ec93a8a6ff0278fab9701dcc71.tmp/CurrenListJMSProducerV1.wsdl [ Produce_Message_ptt::Produce_Message(OutputParameters) ] - : The Adapter Framework was unable to establish an outbound JCA connection due to the following issue: oracle.j2ee.connector.proxy.ProxyInterceptException: javax.resource.ResourceException: RollbackException: Transaction has been marked for rollback: null [Caused by: RollbackException: Transaction has been marked for rollback: null]
Please note that we are not getting this error every time, few BPEL instances are getting this error, around 3 out of 10 instances.
We are using Orcacle 10G SOA suite.
The BPEL process will take the messages from Oracle Apps adapter and send to the JMS queue, where we are getting error.
I can see in the BPEL.xml the "retryInterval" property set to '60' for both partner links (Apps adapter and JMS adapter).
But not set any other values. So,these values may be default.
We need to fix this issue soon.
I am requesting you all the Experts and Gurus, please let me know what can be done to fix this issue.
Thanks a lot in advance,
John.

Hi All,.
Is there any work around for the above issue?
I tried all the below JMS tunings, but not no improvement.
            <property name="useJCAConnectionPool">true</property>
            <property name="maxSizeJCAConnectionPool">500</property>
            <property name="retryMaxCount">10</property>
            <property name="retryInterval">60</property>
Please let
me know if any other logs or any other information is required in order to analyse the issue.
Thanks,
John

Installing SOA Suite on the integrated WLS in JDeveloper

Hi,
I'm wondering if it's possible to install SOA suite on the integrated WebLogic provided with JDeveloper?
If it is not possible, what is the recommended way for provisioning for development? Is it to install a full-blown WebLogic & SOA Suite on each developers' machine?

Hi Mark,
No, it is not possible to install SOA on the integrated WLS in JDeveloper. There are some technical issues preventing it now but we would like to get this working in the future.
So yes, you can install the full WLS + SOA on your own machine for development. After you install, go into WLS and turn off whatever you are not using to shrink the footprint (e.g., you don't need both soa composer and bpm composer, you don't need both worklist and workspace).
Heidi.

Oracle WebLogic Integration's Custom Control and SOA Suite Spring Component

I crated this thread to inform users about some issues with the
Oracle WebLogic Integration's Custom Control and SOA Suite Spring Component
tutorial from
http://www.oracle.com/technology/architect/soa-suite-series/wli_custom_control_spring_component.html
- Fig. 6 doesn't agree with what's just above. This step isn't necessary because it can be create automatically when you make a class.
- Fig. 11 shows the package
sample.oracle.otn.soaessentials.javainteg
and the class should be placed in
sample.oracle.otn.soaessentials.javainteg.impl
- The Business Tier -> Spring 2.5 might not be available. Extensions steps steps should be given.
- Fig. 15 When lgger-context is created in Jdev 11.1.1.3.0 the Spring context is created in
/mywork/SOASuiteWLIEssentials/JavaIntegration/src/META-INF
while in the sample project it is in
/mywork/SOASuiteWLIEssentials/JavaIntegration
- Fig 18 has incorrect class name.
- Fig 19 is incorrect: there is no Spring 2.5 SCA in Jdev 11.1.1.3.0; there is only WebLogic SCA. Where is the canvas mentioned above?
- Fig 28 logger-context.xml is not where it is displayed in the fig. It is /src/Meta-Inf/.
- Most of the fig from the deployment are not up to date.
- I don't understand the need for the portion:
"Implementing the use case in WLI" up to
"Implementing the use case in SOA Suite"
It confused me when I tried to follow the tutorial.

I am also looking for the same .... Please share the CLoning script for SOA Suite from Prod to staging Env...
Thanks.

Installing Oracle SOA Suite with the WebLogic Server

Hi all,
I am trying to install Oracle SOA Suite with the WebLogic Server. After following the step-by-step instruction in the "Installing Oracle SOA Suite with the WebLogic Server" document, I ran into the following situation: I have a working WebLogic Server with all applications deployed. However the BPELPM application is in Failed state.
When I try to run the application, I get following exception (AdminServer.log):
####<Mar 30, 2009 9:46:43 AM EEST> <Warning> <Deployer> <javadev2> <AdminServer> <[STANDBY] ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1238395603163> <BEA-149004> <Failures were detected while initiating start task for application 'BPELPM'.>
####<Mar 30, 2009 9:46:43 AM EEST> <Warning> <Deployer> <javadev2> <AdminServer> <[STANDBY] ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1238395603164> <BEA-149078> <Stack trace for message 149004
weblogic.application.ModuleException: [HTTP:101216]Servlet: "cxloader" failed to preload on startup in Web application: "/orabpel".
javax.servlet.ServletException:
ORABPEL START-UP ERROR!!!!!!!!
OraBPEL run-time system failed to start due to exception:
Bean is already undeployed.
at com.collaxa.cube.admin.CXLoaderServlet.init(CXLoaderServlet.java:87)
at javax.servlet.GenericServlet.init(GenericServlet.java:256)
at weblogic.servlet.internal.StubSecurityHelper$ServletInitAction.run(StubSecurityHelper.java:278)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121)
at weblogic.servlet.internal.StubSecurityHelper.createServlet(StubSecurityHelper.java:64)
at weblogic.servlet.internal.StubLifecycleHelper.createOneInstance(StubLifecycleHelper.java:58)
at weblogic.servlet.internal.StubLifecycleHelper.<init>(StubLifecycleHelper.java:48)
at weblogic.servlet.internal.ServletStubImpl.prepareServlet(ServletStubImpl.java:507)
at weblogic.servlet.internal.WebAppServletContext.preloadServlet(WebAppServletContext.java:1723)
at weblogic.servlet.internal.WebAppServletContext.loadServletsOnStartup(WebAppServletContext.java:1700)
at weblogic.servlet.internal.WebAppServletContext.preloadResources(WebAppServletContext.java:1620)
at weblogic.servlet.internal.WebAppServletContext.start(WebAppServletContext.java:2761)
at weblogic.servlet.internal.WebAppModule.startContexts(WebAppModule.java:889)
at weblogic.servlet.internal.WebAppModule.start(WebAppModule.java:333)
at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:204)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:26)
at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:60)
at weblogic.application.internal.flow.ScopedModuleDriver.start(ScopedModuleDriver.java:200)
at weblogic.application.internal.flow.ModuleListenerInvoker.start(ModuleListenerInvoker.java:117)
at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:204)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:26)
at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:60)
at weblogic.application.internal.flow.StartModulesFlow.activate(StartModulesFlow.java:26)
at weblogic.application.internal.BaseDeployment$2.next(BaseDeployment.java:635)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:26)
at weblogic.application.internal.BaseDeployment.activate(BaseDeployment.java:212)
at weblogic.application.internal.DeploymentStateChecker.activate(DeploymentStateChecker.java:154)
at weblogic.deploy.internal.targetserver.AppContainerInvoker.activate(AppContainerInvoker.java:80)
at weblogic.deploy.internal.targetserver.operations.AbstractOperation.activate(AbstractOperation.java:566)
at weblogic.deploy.internal.targetserver.operations.ActivateOperation.activateDeployment(ActivateOperation.java:136)
at weblogic.deploy.internal.targetserver.operations.ActivateOperation.doCommit(ActivateOperation.java:104)
at weblogic.deploy.internal.targetserver.operations.StartOperation.doCommit(StartOperation.java:139)
at weblogic.deploy.internal.targetserver.operations.AbstractOperation.commit(AbstractOperation.java:320)
at weblogic.deploy.internal.targetserver.DeploymentManager.handleDeploymentCommit(DeploymentManager.java:815)
at weblogic.deploy.internal.targetserver.DeploymentManager.activateDeploymentList(DeploymentManager.java:1222)
at weblogic.deploy.internal.targetserver.DeploymentManager.handleCommit(DeploymentManager.java:433)
at weblogic.deploy.internal.targetserver.DeploymentServiceDispatcher.commit(DeploymentServiceDispatcher.java:161)
at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.doCommitCallback(DeploymentReceiverCallbackDeliverer.java:181)
at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.access$100(DeploymentReceiverCallbackDeliverer.java:12)
at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer$2.run(DeploymentReceiverCallbackDeliverer.java:67)
at weblogic.work.ServerWorkManagerImpl$WorkAdapterImpl.run(ServerWorkManagerImpl.java:518)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:181)
at weblogic.servlet.internal.WebAppModule.startContexts(WebAppModule.java:891)
at weblogic.servlet.internal.WebAppModule.start(WebAppModule.java:333)
at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:204)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:26)
at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:60)
at weblogic.application.internal.flow.ScopedModuleDriver.start(ScopedModuleDriver.java:200)
at weblogic.application.internal.flow.ModuleListenerInvoker.start(ModuleListenerInvoker.java:117)
at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:204)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:26)
at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:60)
at weblogic.application.internal.flow.StartModulesFlow.activate(StartModulesFlow.java:26)
at weblogic.application.internal.BaseDeployment$2.next(BaseDeployment.java:635)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:26)
at weblogic.application.internal.BaseDeployment.activate(BaseDeployment.java:212)
at weblogic.application.internal.DeploymentStateChecker.activate(DeploymentStateChecker.java:154)
at weblogic.deploy.internal.targetserver.AppContainerInvoker.activate(AppContainerInvoker.java:80)
at weblogic.deploy.internal.targetserver.operations.AbstractOperation.activate(AbstractOperation.java:566)
at weblogic.deploy.internal.targetserver.operations.ActivateOperation.activateDeployment(ActivateOperation.java:136)
at weblogic.deploy.internal.targetserver.operations.ActivateOperation.doCommit(ActivateOperation.java:104)
at weblogic.deploy.internal.targetserver.operations.StartOperation.doCommit(StartOperation.java:139)
at weblogic.deploy.internal.targetserver.operations.AbstractOperation.commit(AbstractOperation.java:320)
at weblogic.deploy.internal.targetserver.DeploymentManager.handleDeploymentCommit(DeploymentManager.java:815)
at weblogic.deploy.internal.targetserver.DeploymentManager.activateDeploymentList(DeploymentManager.java:1222)
at weblogic.deploy.internal.targetserver.DeploymentManager.handleCommit(DeploymentManager.java:433)
at weblogic.deploy.internal.targetserver.DeploymentServiceDispatcher.commit(DeploymentServiceDispatcher.java:161)
at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.doCommitCallback(DeploymentReceiverCallbackDeliverer.java:181)
at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.access$100(DeploymentReceiverCallbackDeliverer.java:12)
at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer$2.run(DeploymentReceiverCallbackDeliverer.java:67)
at weblogic.work.ServerWorkManagerImpl$WorkAdapterImpl.run(ServerWorkManagerImpl.java:518)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:181)
Any help would be highly appreciated.
Boris

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

OSB and SOA Suite in the Java Cloud

Similar Messages

Maybe you are looking for