Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > comp.lang.javascript > #86506 > unrolled thread

Oracle Soa Composite Editor For Jdeveloper 12c Download

Back to article view | Back to comp.lang.javascript

Contents

  Oracle Soa Composite Editor For Jdeveloper 12c Download Liv Mathenia <mathenialiv@gmail.com> - 2024-01-06 03:22 -0800

#86506 — Oracle Soa Composite Editor For Jdeveloper 12c Download

2) Downloaded SOA Composite 11.1.1.9.0.99.99 Editor from below url for JDEVLOPER 12c, as I could not find 12c extension thinking 11 ext will work for 12c  otn/documents/webcontent/156082.xml#oracle.sca.modeler


This chapter describes the functionality of the SOA Composite Editor by guiding you through the creation of service components, binding components, and wires in an SOA composite application. This chapter also describes key issues to be aware of when designing your application.



oracle soa composite editor for jdeveloper 12c download

Download File https://t.co/czer2KiUh0 






This section provides an overview of how to create and design an SOA composite application in Oracle JDeveloper. This overview is intended to guide you through the basic steps of component creation, along with describing key issues to be aware of when designing a composite application.


A project deployed to the same infrastructure must have a unique name across SOA composite applications. This is because the uniqueness of a composite is determined by its project name. For example, do not perform the actions described in Table 4-3. During deployment, the second deployed project (composite) overwrites the first deployed project (composite).


The SOA Composite Editor shown in Figure 4-2 appears. The composite.xml file displays in the Application Navigator. This file is automatically created when you create a project. This file describes the entire composite assembly of services, service components, and references. There is one composite.xml file per SOA project.


To return to the SOA Composite Editor from within any service component, click Go to Composite Editor on the tool bar. You can also double-click composite.xml in the Application Navigator or single-click composite.xml above the designer.


A WSDL file is added to the SOA composite application whenever you create a new component that has a WSDL (for example, a service binding component, service component (for example, Oracle Mediator, BPEL process, and so on), or reference binding component. When you delete a component, any WSDL imports used by that component are removed only if not used by another component. The WSDL import is always removed when the last component that uses it is deleted.


Simply changing the WSDL location on the source view of the composite.xml file's import is not sufficient. Other WSDL references in the metadata are required by the user interface (see the ui:wsdlLocation attribute on composite and componentType services and references). There can also be other WSDL references required by runtime (for example, a WSDL that imports another WSDL, such as the BPEL process WSDL).






A WSDL URL that does not contain a revision number is processed by the default composite application. This action enables you to always call the default revision of the called service without having to make other changes in the calling composite.


Not doing so results in the hard-coded references of the revision number of the service being called in the calling composite. This binds it to always call that particular revision even if the default revision of the called service changes after deployment.


You cannot wire services and composites that have different interfaces. For example, you cannot connect a web service configured with a synchronous WSDL file to an asynchronous BPEL process. Figure 4-12 provides details.


You can manage deployed SOA composite applications from the Application Server Navigator in Oracle JDeveloper. Management tasks consist of deploying, undeploying, activating, retiring, turning on, and turning off SOA composite application revisions.


The deployments and SOA folders appear, as shown in Figure 4-21. The SOA folder displays all deployed SOA composite application revisions and services. You can browse all applications deployed on all Oracle WebLogic Administration Servers, managed Oracle WebLogic Servers, and clustered Oracle WebLogic Servers in the same domain. Figure 4-21 provides details.


An initiating request to the composite application is rejected back to the client. The behavior of different binding components during rejection is equal to that described above for the shut down option.


If you want to deploy a prebuilt SOA composite application archive that includes a deployment profile, right-click the SOA folder and select Deploy SOA Archive. The archive consists of a JAR file of a single application or an SOA bundle ZIP file containing multiple applications.


You can run and test instances of deployed SOA composite applications from Oracle Enterprise Manager Grid Control Console. For more information about testing an SOA composite application, see Oracle Fusion Middleware Administrator's Guide for Oracle SOA Suite.


Remember I said 256 was not enough? Before you run into trouble with that memory adjustment, edit the file /jdeveloper/jdev/bin/jdev.conf and change the attribute -XX:MaxPermSize to 1024, just like you see in the picture(You are free to put any value you want really, but do it at your own risk):


Open JDeveloper. To open JDeveloper, navigate to middleware home folder\jdeveloper\ and jdeveloper.exe. This will open up the JDeveloper tool. This will ask you to select Role. Just accept the defautl value and click Ok. On JDeveloper Help menu and then select Check for Updates.




In the previous examples, we created a JMS Queue, a Connection Factory and a Connection Pool in the WebLogic Server Console. Then we designed and deployed a BPEL composite, which took a simple XML

payload and enqueued it to the JMS queue. In this example, we will read that same message from the queue, using a JMS adapter and a BPEL process. As many of the configuration steps required to read

from that queue were done in the previous samples, this one will concentrate on the new steps. A summary of the required objects is listed below. To find out how to create them please see the previous samples. They also include instructions on how to verify the objects are set up correctly.


There are probably many ways of incorporating a JMS adapter into a SOA composite for incoming messages. One way is design the process in such a way that the adapter polls for new messages and when it dequeues one, initiates a SOA or BPEL instance. This is possibly the most common use case. Other use cases include mid-flow adapters, which are activated from within the BPEL process. In this example we will use a polling adapter, because it is the most simple to set up and demonstrate. But it has one disadvantage as a demonstrative model. When a polling adapter is active, it will dequeue all messages as soon as they reach the queue. This makes it difficult to monitor messages we are writing to the queue, because they will disappear from the queue as soon as they have been enqueued. To work around this, we will shut down the composite after deploying it and restart it as required. (Another solution for this would be to pause

the consumption for the queue and resume consumption again if needed. This can be done in the WLS console JMS-Modules -> queue

-> Control -> Consumption -> Pause/Resume.)


Drag a BPEL Process from the Component Palette (Service Components) to the Components section of the composite designer. Name it

JmsAdapterReadSchema and select Template: Define Service Later and press OK.


Open the BPEL component by double-clicking it in the design view of the composite.xml, or open it from the project navigator by selecting the JmsAdapterReadSchema.bpel file. This will display the BPEL process in the design view. You should see the JmsAdapterRead partner link in the left-hand swim lane.


After deploying the JmsAdapterReadSchema composite to the SOA server it is automatically activated. If there are already any messages in the queue, the adapter will begin polling them. To ease the testing process, we will deactivate the process first


Log in to the Enterprise Manager (Fusion Middleware Control) and navigate to SOA > soa-infra (soa_server1) > default (or

wherever you deployed your composite to) and click on JmsAdapterReadSchema [1.0]. Press the Shut Down button to disable the composite and confirm the following popup.


In the previous examples, we created a JMS Queue, a Connection Factory and a Connection Pool in the WebLogic Server Console. Then we designed and deployed a BPEL composite, which took a simple XML

\npayload and enqueued it to the JMS queue. In this example, we will read that same message from the queue, using a JMS adapter and a BPEL process. As many of the configuration steps required to read

\nfrom that queue were done in the previous samples, this one will concentrate on the new steps. A summary of the required objects is listed below. To find out how to create them please see the previous  samples. They also include instructions on how to verify the objects are set up correctly.


There are probably many ways of incorporating a JMS adapter into a  SOA composite for incoming messages. One way is design the process in such a way that the adapter polls for new messages and when it dequeues one, initiates a SOA or BPEL instance. This is possibly the most common use case. Other use cases include mid-flow adapters, which are activated from within the BPEL process. In this example we will use a polling adapter, because it is the most simple to set up and demonstrate. But it has one disadvantage as a demonstrative model. When a polling adapter is active, it will dequeue all messages as soon as they reach the queue. This makes it difficult to monitor messages we are writing to the queue, because they will disappear from the queue as soon as they have been enqueued. To work around this, we will shut down the composite after deploying it and restart it as required. (Another solution for this would be to pause

\nthe consumption for the queue and resume consumption again if needed. This can be done in the WLS console JMS-Modules -> queue

\n-> Control -> Consumption -> Pause/Resume.)


We will model the composite as a one-way incoming process. Usually, a BPEL process will do something useful with the message after

\nreceiving it, such as passing it to a database or file adapter, a human workflow or external web service. But we only want to demonstrate how to dequeue a JMS message using BPEL and a JMS adapter, so we won’t complicate the design with further activities. However, we do want to be able to verify that we have read the message correctly, so the BPEL process will include a small piece of embedded java code, which will print the message to standard output, so we can view it in the SOA server’s log file. Alternatively, you can view the instance in the Enterprise Manager and verify the message.

 35fe9a5643

[toc] | [standalone]

Back to top | Article view | comp.lang.javascript

csiph-web