composite deployment oracle soa suite 11g/12c · lists all soa composite applications deployed to...

Composite Deployment Oracle SOA Suite 11g/12cCON8701

Antonella GiovannettiAntonella GiovannettiSenior Technical Support EngineerOracle Support, SOA Proactive ServicesOctober, 2015

Oracle Confidential – Internal/Restricted/Highly RestrictedCopyright © 2015, Oracle and/or its affiliates. All rights reserved. |

Safe Harbor Statement

The following is intended to outline our general product direction. It is intended for information purposes only, and may not be incorporated into any contract. It is not a commitment to deliver any material, code, or functionality, and should not be relied upon

Copyright © 2015, Oracle and/or its affiliates. All rights reserved. |

commitment to deliver any material, code, or functionality, and should not be relied upon in making purchasing decisions. The development, release, and timing of any features or functionality described for Oracle’s products remains at the sole discretion of Oracle.

3

Program Agenda

From Design to Runtime

From One to Many Environments

Managing Deployed Composites

1

2

3



Troubleshooting

Additional Resources

Q&A

3

4

5

6

4


PrepareTarget Environment

Package

SOA Composite(s)

Deploy

SOA Composite(s)


SOA Composite Target Environment

5


• SOA Domain with Admin and Managed WebLogic Servers

• Single Server or Clustered Environment

Requirements

Preparing


• WLS servers must be able to connect to the SOA Database Schema.

• DB Schema must have at least one Partition. Oracle SOA Suite automatically includes a partition called default.

6


• Database Adapter and AQ Adapter

– JDBC Data Sources and JDBC Connection Pools

• JMS Adapter

– Queues to Enqueue / Dequeue Messages

Preparing

Resources


• Human Workflow

– Configure alternative identity service provider (Oracle Internet Directory, Microsoft Active Directory, or Oracle iPlanet). WebLogic embedded LDAP (default) is not supported in a SOA cluster

• OWSM

– Configure OWSM policies for Authentication / Authorization

• B2B

– Deploy B2B Trading Partner Agreements from design-time to the run-time repository

7

• Types of archive files:

– SOA Archive (SAR): single composite. Special JAR file with the prefix sca_.

sca_<composite name>_rev<version ID>.jar

– ZIP file: multiple composites. Contains multiple SARs and/or Metadata Archives (MARs)

Deployable Archives

From Design to Runtime Packaging


– ZIP file: multiple composites. Contains multiple SARs and/or Metadata Archives (MARs)

• Artifacts Included:

– Binding and Service Components

– References to Oracle B2B agreements, OWSM policies, and human workflow task flows.

–WSDL and XSD files

8

• Oracle JDeveloper

• WLST Commands

Packaging Tools



• ANT Scripts

• Maven Plug-In

9

12c

• Oracle Jdeveloper

– Right-click the SOA project -> Deploy -> Deploy to SAR

• Creates the SAR file but does NOT deploy to Application Server

• Useful when:

Packaging Tools



• Useful when:

– Admin Server is not running, but you want to create the archive file.

– Need to create the archive file to deploy from the FMW Control Console.

10

ToolScript/

CommandSyntax Example Result

ANT (*) ant-sca-package

ant -f ant-sca-package.xml

-DcompositeDir

-DcompositeName

-Drevision

[-Dsca.application.home ]

ant -f ant-sca-package.xml

-DcompositeDir=/tmp/HelloSOAApplication/

-DcompositeName=HelloSOAComposite

-Drevision=1.0sca_HelloSOAComposite_rev1.0.jar

ANT and WLST

From Design to RuntimePackaging


[-Dsca.application.home ] (**)

[-Doracle.home]

-Drevision=1.0

WLST sca-package

sca_package(

compositeDir,

compositeName,

revision,

[appHome], (**)

[oracleHome])

sca_package (

"/tmp/HelloSOAApplication/",

"HelloSOAComposite",

“1.0”)

sca_HelloSOAComposite_rev1.0.jar

11

(*) Run SetDomianEnv before running ant scripts. It adds necessary JAR files to the classpath

(**) Required if composite accesses shared artifacts in the MDS repository

• Maven Plug-In

– Uses archetypes to compile, package, deploy, test, and undeploy a SOA composite application.

–More information:

Packaging Tools


12c


–More information:

Developing SOA Applications with Oracle SOA Suite

48 Using the Oracle SOA Suite Development Maven Plug-In

12

• Deployment Tools

– JDeveloper (single/multiple SOA applications and Shared Data)

–WLST Commands

– ANT Scripts

Deployment

From Design to Runtime Deployment


– ANT Scripts

– FMW Control

–Maven Plug-In

• Offline Deployment

• Multi-Tenancy Deployment

13

12c

12c

12c

• Create a Project Deployment Profile

• Deploy the Profile to the Application Server

JDeveloper – Single application


Copyright © 2015, Oracle and/or its affiliates. All rights reserved. | 14

• Create SOA Bundle Profile includes two or more SAR files (ZIP)

– From the Application menu, select Application Properties -> Deployment

– Select the composites

JDeveloper – Multiple applications



• Deploy the bundle. Application > Deploy > SOA_Bundle_Name

15

• You cannot deploy applications that are dependent upon one another in the same SOA bundle profile. For example, if application A calls application B, then you must first deploy application B separately.

JDeveloper – Multiple Applications



• Create a JAR with the shared data (WSDLs, XSDs, etc.) called a MAR.

• Create a bundle with the composite and the MAR file and then deploy.

JDeveloper – Applications Sharing Data



Command Use Example

sca_deployCompositeDeploy a SOA composite application.

Does not do the packing

sca_deployComposite("http://myhost10:7001", "/tmp/sca_HelloWorld_rev1.0.jar“,

forceDefault=“true”, partition ="myPartition“,

overwrite=“false”,

configplan=“C:\demo\POProcessing\cfgplan.xml”)

WLST Commands

From Design to RuntimeDeployment


sca_undeployCompositeUndeploys a currently deployed SOA

composite applicationsca_undeployComposite("http://myhost10:7001", "HelloWorld", "1.0")

sca_listDeployedCompositesLists all SOA composite applications

deployed to the SOA platformsca_listDeployedComposites('myhost', '7001', 'weblogic', 'welcome1')

Complete List:Oracle Fusion Middleware WebLogic Scripting Tool Command Reference9 Oracle SOA Suite Custom WLST Commands

18

Scripts Use Example

ant-sca-deploy.xml

Deploy a SOA composite

application.

Does not do the packing

ant -f ant-sca-deploy.xml

-DserverURL=http://localhost:8001

-DsarLocation=C:\demo\POProcessing\deploy\sca_POProcessing_rev6.jar

-Duser=weblogic

-DforceDefault =true

-Dpartition= default

-Doverwrite=false

-Dconfigplan =C:\demo\POProcessing\cfgplan.xml

ANT Scripts

From Design to RuntimeDeployment


-Dconfigplan =C:\demo\POProcessing\cfgplan.xml

ant-sca-deploy.xml undeploy

Undeploys a currently

deployed SOA composite

application

ant -f ant-sca-deploy.xml undeploy -DserverURL=http://localhost:8001

-DcompositeName=POProcessing -Drevision=6

-Duser=weblogic -Dpartition=default

ant-sca-mgmt.xml listDeployedComposites

Lists all SOA composite

applications deployed to

the SOA platform

ant -f ant-sca-mgmt.xml listDeployedComposites -Dhost=myhost -Dport=8001 -Duser=weblogic

Complete List:Oracle® Fusion Middleware Developer's Guide for Oracle SOA Suite 11g Release 1 (11.1.1.9)43.7.6 How to Manage SOA Composite Applications with ant Scripts

19


• Requires the application(s) to be already packaged in a SAR or ZIP file.

• Use to Deploy:

FMW Control Console

Deployment


• Use to Deploy:– A new revision (for example, 2.0) alongside an older revision (for example, 1.0). The

last deployed revision becomes the default revision unless otherwise specified.

– A SOA bundle (ZIP file) containing revisions of different composites (dependencies are not allowed)

20

• Deployment is available from different places in the console:

1. SOA Infrastructure Menu > SOA Deployment > Deploy

2. SOA Folder in the Navigator > Right-click soa-infra > SOA Deployment > Deploy

3. SOA Infrastructure Home Page > Deployed Composites tab > Deploy

From Design to RuntimeFMW Control Console

Deployment


3. SOA Infrastructure Home Page > Deployed Composites tab > Deploy

4. SOA Composite Menu > SOA Deployment > Deploy Another Composite

21

• Configuration files:

– soa-configuration.xml

• Stored in the $DOMAIN/config/fmwconfig

From Design to RuntimeOffline Deployment

Deployment

• Admin and Managed servers are not running. Deployment done at startup.

12c


• Stored in the $DOMAIN/config/fmwconfigdirectory

• Locations of composite offline deployment configuration files

– composite-offline-deployments-version_number.xml

• Deployment directives (partitions, shared resources, SOA composites)

22

• Can use WLST commands to add and remove composites and shared data from offline deployments

• SOA Composites are deployed to all nodes in the cluster

• Can not redeploy or undeploy SOA composites

From Design to RuntimeOffline Deployment

Deployment


• Can not redeploy or undeploy SOA composites

• Can redeploy shared data since there is no revision concept

23

From Design to RuntimeMulti-Tenancy Deployment

Deployment

Web Tier

Virtual Host-1

soa-infra

Virtual Host-2

Partition 1 Partition 2

WLS Managed Server/Cluster

Global

soa-infra-bootstrap soa-infra

Virtual Host-G

• When connected to WLS host

deploys to the global partition

• When connected to tenant virtual

12c


Container Database

PDB1 PDB2

soa-infra

Tenant cache

JMS

Datasource

JNDI

Global PDB

Shared cache

JCA Factories

MDS MDS MDSDehydration Dehydration

soa-infra-bootstrap soa-infra

Tenant cache

JMS

Datasource

JNDI

JCA Factories

JMS

Datasource

JNDI

JCA Factories

• When connected to tenant virtual

host deploys a tenant composite

• Use WLST, ANT, FMW Control for

deployment

Program Agenda




1

2

3



Troubleshooting


Q&A

3

4

5

6

25


• Configuration Plans

– Replaces values at the composite level.

– Values are replaced during deployment and stored in the SOA schema.


• Global Token Variables

– Replaces specific URIs in all the composites

– Values are replaced at runtime when loading the composites

26


• XML file with environment-specific values, like connection strings, hostnames, ports, etc.

• Replaces values in the composite.xml, WSDL, and XSD files during deployment. Does not work on XSLT artifacts.

Configuration Plans


deployment. Does not work on XSLT artifacts.

• Tools

– Jdeveloper : Create Configuration Plan and Validate Configuration Plan.

–WLST: sca_generatePlan, sca_attachPlan, sca_validatePlan, sca_extractPlan.

27


• Attached to the SOA archive file when deploying

Configuration Plans


• Properties that can be replaced:

– Any composite properties, service component, reference, and binding properties in the composite.xml file.

– Attribute values for bindings (e.g., location)

From One to Many EnvironmentsConfiguration Plans


– Attribute values for bindings (e.g., location)

– schemaLocation attribute of an import in a WSDL file.

– location attribute of an include in a WSDL file.

– schemaLocation attribute of an include, import, and redefine session in an XSD file.

– Any properties in JCA adapter files.

– Policy references for Service and Reference binding components.

29


Replaces endpoints and locations in all references in all WSDL, XSD and JCA files

Configuration Plans

<SOAConfigPlan ….>

<composite name="*">

<reference name="*">

<binding type="ws">

<property name="endpointURI">

<searchReplace>

<search>http://DevEnv </search>


<search>http://DevEnv </search>

<replace>http://TestEnv </replace>

</searchReplace>

</property>

</binding>

</reference>

<reference name="*">

<binding type="ws">

<attribute name="location">

<searchReplace>

<search>http://DevEnv</search>

<replace>http://TestEnv </replace>

</searchReplace>

:

</composite>

</SOAConfigPlan>

30


• Advantage

– Each composite can have a configuration plan for each environment (Development, Test, QA, Production, etc)

• Disadvantage

Configuration Plans


• Disadvantage

– Changes in an environment will require changing the configuration files of each of the composites deployed to that environment.

–Metadata deployed on the runtime server will include environment-specific values.

31


• List of key-value pairs. Custom or Predefined (ServerURL and applicationURL)

• Replaces specific URIs in all the composites.

• Replaces any token in the composite.xml file except those in the import

Global Token Variables


• Replaces any token in the composite.xml file except those in the import element.

• Only host, port, and protocol at the ws.binding location and any property under the reference tag.

• Tokens are defined in the FMW Control console and stored in the

$MIDDLEWARE_HOME/user_projects/domains/<domain_name>/config/fmwconfig/mdm-url-resolver.xml

32

<properties> <entry key="myprotocol">http</entry> <entry key="myhost">mymachine.us.example.com</entry> <entry key="myport">8001</entry>

<composite...> . . . . . . <reference name="Service" ui:wsdlLocation="..."> . . . <binding.ws port="..."

location="${myprotocol}://${myhost}:${myport}/soa-infra/services/default/mycomposite/bpelprocess1_client_ep?WSDL" soapVersion="1.1">

</binding.ws>

From One to Many EnvironmentsGlobal Token Variables

mdm-url-resolver.xml Composite.xml


<entry key="myport">8001</entry> </properties>

bpelprocess1_client_ep?WSDL" soapVersion="1.1"> </binding.ws> </reference> . . .</composite>

http://mymachine.us.example.com:8001/soa-infra/services/default/mycomposite/ bpelprocess1_client_ep?WSDL

33


• Advantages:

–No need to change multiple configuration plans when multiple composites refer to a same service.

–Metadata deployed on the runtime server will not include environment-specific

Global Token Variables


–Metadata deployed on the runtime server will not include environment-specific values.

– In a clustered environment, global token variable changes are made on the administration server and propagated to all managed servers.

34

Program Agenda




1

2

3



Troubleshooting


Q&A

3

4

5

6

35


• Redeploy - overwrites a existing composite with the same revision ID

• Undeploy - removes a revision of the composite and all related artifacts


More Information:

Oracle® Fusion Middleware Administrator's Guide for Oracle SOA Suite and Oracle Business Process Management Suite

12c Release 2 (12.2.1)

10.5 Managing the State of Deployed SOA Composite Applications


• Jdeveloper, ANT, WLST (deploy operation + overwrite)

• FMW Console (redeploy operation)

Redeploy



• If the deployed revision has instances in running, recovery or suspendedstate then the state will change to Stale (11g)/Aborted (12c)

– Instances will remain in running state only if: – Composite doesn’t have a durable BPEL process (asynchronous or synchronous with durable activity)

Redeploy

12c


– Composite doesn’t have a durable BPEL process (asynchronous or synchronous with durable activity)

– Composite has a durable BPEL process but the process has not changed

– Partner links and Dehydration activities have not changed since the last deployment.

• You can still access audit and flow trace details of the instances

38


1. Redeploy Composite with Synchronous BPEL

• Old running instance are not marked as aborted. Audit trail has old process execution

• New instances will show new process execution

2. Redeploy Composite with Asynch BPEL with a Receive activity

Redeploy Examples 12c


2. Redeploy Composite with Asynch BPEL with a Receive activity

• Change process after receive activity

– Old running instance are not marked as aborted. Audit trail has old process execution

– New instances will show new process execution

– Instances waiting on recv1 continue using new process definition

• Delete receive activity

– Redeployment fails

39


• JDeveloper, WLST, ANT and FMW Console

• Rules:

– Running instances are changed to Stale(11g)/Aborted(12c). No new messages are processed.

Undeploy


– Running instances are changed to Stale(11g)/Aborted(12c). No new messages are processed.

– Cannot view previously completed instances.

– Cannot configure and monitor a composite after it is undeployed.

– Undeploying default revision -> next active revision becomes new default.

– Undeploying default revision with no active revision -> retired revision becomes new default.

Need to reactivate to process new messages.

– Can undeploy multiple SOA composites located in the same partition.

40

Program Agenda




1

2

3



Troubleshooting


Q&A

3

4

5

6

41

Troubleshooting

• Set following loggers to TRACE 32 in FMW Console:

–Oracle.soa.bpel.deployment

–Oracle.soa.bpel.compiler

– oracle.integration.platform.blocks.deploy

Debug and Log Files


– oracle.integration.platform.blocks.deploy

• Check for error messages in:

– DOMAIN_HOME/servers/<server-name>/logs/<server-name>.log

– DOMAIN_HOME/servers/<server-name>/logs/<server-name>-diagnostic.log

•42

Troubleshooting

• SOA-20020 ... Unable to find a WSDL that has a definition for service xxx

• SOA-20003 ... Unable to register service xxx .. Error in getting XML input stream

• The composite xxx is not available

Error Codes


• The composite xxx is not available

• java.lang.RuntimeException: java.lang.Exception: BPEL 1.1 compilation failed

• javax.net.ssl.SSLKeyException: FATAL Alert:BAD_

43

TroubleshootingSolutions – My Oracle Support (http://support.oracle.com)


TroubleshootingSolutions – My Oracle Support


Troubleshooting

• Problem

Configuration plan is not taking effect during deployment

• Cause

Selected the wrong configuration plan


Selected the wrong configuration plan

• Solution

–Open SAR file and ensure it contains the soaconfigplan.xml file.

– Ensure you select the configuration plan in the Deploy Configuration page of the Deployment Wizard.

46

Troubleshooting

• Problem

Deployment cannot continue! No SOA Configured target servers found

• Cause

– Used JDeveloper for deployment and Admin Server is not running or is in WARNING state


WARNING state

• Solutions

– Start the Admin Server

– If you need to run Managed Server in Independent mode then use WLST to deploy to a Managed Server

47

Troubleshooting

• Problem

oracle.fabric.common.FabricException: Timed out waiting for operation to complete… CompositeDeploymentCoordinatorMessages.throwTimedOutWaiting

• Cause

Coherence configuration is not correct. You maybe missing one or more of these


Coherence configuration is not correct. You maybe missing one or more of these parameters : tangosol.coherence.wka, tangosol.coherence.localhost, tangosol.coherence.localport)

• Solution

OracleFusion Middleware Enterprise Deployment Guide for Oracle SOA Suite 11g Release 1 (11.1.9.0)

9.4 Configuring Oracle Coherence for Deploying Composites

48

Program Agenda




1

2

3



Troubleshooting


Q&A

3

4

5

6

49


• Oracle® Fusion Middleware Administrator's Guide for Oracle SOA Suite and Oracle Business Process Management Suite11g Release 1 (11.1.1.9) and 12c (12.2.1)

• Oracle® Fusion Middleware Developer's Guide for Oracle SOA Suite11g Release 1 (11.1.1.9) and 12c (12.2.1)


11g Release 1 (11.1.1.9) and 12c (12.2.1)

• Deploying a SOA Composite Application Video (OLL YouTube Channel)

• Follow us on Twitter @soaproactive or SOA Proactive Blog

50

Q&A


composite deployment oracle soa suite 11g/12c · lists all soa composite applications deployed to...

Documents