Composite Deployment Oracle SOA Suite 11g/12c

Transcription

1

2 Composite Deployment Oracle SOA Suite 11g/12c CON8701 Antonella Giovannetti Senior Technical Support Engineer Oracle Support, SOA Proactive Services October, 2015 Oracle Confidential Internal/Restricted/Highly Restricted

3 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 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

4 Program Agenda From Design to Runtime From One to Many Environments Managing Deployed Composites Troubleshooting Additional Resources Q&A 4

5 From Design to Runtime Prepare Target Environment Package SOA Composite(s) Deploy SOA Composite(s) SOA Composite Target Environment 5

6 From Design to Runtime Requirements Preparing SOA Domain with Admin and Managed WebLogic Servers Single Server or Clustered Environment 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

7 From Design to Runtime Resources Database Adapter and AQ Adapter JDBC Data Sources and JDBC Connection Pools JMS Adapter Queues to Enqueue/ Dequeue Messages Human Workflow Preparing 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

8 From Design to Runtime Deployable Archives Packaging 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) Artifacts Included: Binding and Service Components References to Oracle B2B agreements, OWSM policies, and human workflow task flows. WSDL and XSD files 8

9 From Design to Runtime Packaging Tools Packaging Oracle JDeveloper WLST Commands ANT Scripts Maven Plug-In 12c 9

10 From Design to Runtime Packaging Tools Packaging Oracle Jdeveloper Right-click the SOA project -> Deploy -> Deploy to SAR Creates the SAR file but does NOT deploy to Application Server 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

11 From Design to Runtime ANT and WLST Packaging Tool Script/ Command Syntax Example Result ANT (*) ant-sca-package ant -f ant-sca-package.xml -DcompositeDir -DcompositeName -Drevision [-Dsca.application.home ] (**) [-Doracle.home] ant -f ant-sca-package.xml -DcompositeDir=/tmp/HelloSOAApplication/ -DcompositeName=HelloSOAComposite -Drevision=1.0 sca_hellosoacomposite_rev1.0.jar WLST sca-package sca_package( compositedir, compositename, revision, [apphome], (**) [oraclehome]) sca_package ( "/tmp/hellosoaapplication/", "HelloSOAComposite", 1.0 ) sca_hellosoacomposite_rev1.0.jar (*) Run SetDomianEnv before running ant scripts. It adds necessary JAR files to the classpath (**) Required if composite accesses shared artifacts in the MDS repository 11

12 From Design to Runtime Packaging Tools Packaging Maven Plug-In 12c Uses archetypes to compile, package, deploy, test, and undeploya SOA composite application. More information: Developing SOA Applications with Oracle SOA Suite 48 Using the Oracle SOA Suite Development Maven Plug-In 12

13 From Design to Runtime Deployment Deployment Deployment Tools JDeveloper(single/multiple SOA applications and Shared Data) WLST Commands ANT Scripts FMW Control 12c Maven Plug-In Offline Deployment Multi-Tenancy Deployment 12c 12c 13

14 From Design to Runtime JDeveloper Single application Deployment Create a Project Deployment Profile Deploy the Profile to the Application Server 14

15 From Design to Runtime JDeveloper Multiple applications Deployment Create SOA Bundle Profile includes two or more SAR files (ZIP) From the Application menu, select Application Properties -> Deployment Select the composites Deploy the bundle. Application > Deploy > SOA_Bundle_Name 15

16 From Design to Runtime JDeveloper Multiple Applications Deployment You cannotdeploy applications that are dependentupon one another in the same SOA bundle profile. For example, if application A calls application B, then you must first deploy application B separately. 16

17 From Design to Runtime JDeveloper Applications Sharing Data Deployment 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. 17

18 From Design to Runtime WLST Commands Deployment Command Use Example sca_deploycomposite Deploy a SOA composite application. Does not do the packing sca_deploycomposite(" "/tmp/sca_helloworld_rev1.0.jar, forcedefault= true, partition="mypartition, overwrite= false, configplan= C:\demo\POProcessing\cfgplan.xml ) sca_undeploycomposite Undeploysa currently deployed SOA composite application sca_undeploycomposite(" "HelloWorld", "1.0") sca_listdeployedcomposites Lists all SOA composite applications deployed to the SOA platform sca_listdeployedcomposites('myhost', '7001', 'weblogic', 'welcome1') Complete List: Oracle Fusion Middleware WebLogic Scripting Tool Command Reference 9 Oracle SOA Suite Custom WLST Commands 18

19 From Design to Runtime ANT Scripts Deployment Scripts Use Example ant-sca-deploy.xml Deploy a SOA composite application. Does not do the packing ant -f ant-sca-deploy.xml -DserverURL= -DsarLocation=C:\demo\POProcessing\deploy\sca_POProcessing_rev6.jar -Duser=weblogic -DforceDefault =true -Dpartition= default -Doverwrite=false -Dconfigplan=C:\demo\POProcessing\cfgplan.xml ant-sca-deploy.xml undeploy Undeploysa currently deployed SOA composite application ant -f ant-sca-deploy.xml undeploy-dserverurl= -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 ( ) How to Manage SOA Composite Applications with ant Scripts 19

20 From Design to Runtime FMW Control Console Deployment Requires the application(s) to be already packaged in a SAR or ZIP file. 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

21 From Design to Runtime FMW Control Console Deployment 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 4. SOA Composite Menu > SOA Deployment > Deploy Another Composite 21

22 From Design to Runtime Offline Deployment 12c Deployment Admin and Managed servers are not running. Deployment done at startup. Configuration files: soa-configuration.xml Stored in the $DOMAIN/config/fmwconfig directory Locations of composite offline deployment configuration files composite-offline-deploymentsversion_number.xml Deployment directives (partitions, shared resources, SOA composites) 22

23 From Design to Runtime Offline Deployment Deployment 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 Can redeploy shared data since there is no revision concept 23

24 From Design to Runtime Multi-Tenancy Deployment When connected to WLS host deploys to the global partition When connected to tenant virtual host deploys a tenant composite Use WLST, ANT, FMW Control for deployment 12c WLS Managed Server/Cluster Web Tier Virtual Host-1 Virtual Host-G Partition 1 Global Partition 2 soa-infra Tenant cache JNDI JMS JNDI JCA Factories Datasource soa-infra-bootstrap Shared cache JNDI JMS JCA Factories Datasource Deployment Virtual Host-2 soa-infra Tenant cache JMS JCA Factories Datasource PDB1 Global PDB MDS Dehydration MDS MDS Container Database PDB2 Dehydration 24

25 Program Agenda From Design to Runtime From One to Many Environments Managing Deployed Composites Troubleshooting Additional Resources Q&A 25

26 From One to Many Environments 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

27 From One to Many Environments Configuration Plans 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. Tools Jdeveloper: Create Configuration Plan and Validate Configuration Plan. WLST: sca_generateplan, sca_attachplan, sca_validateplan, sca_extractplan. 27

28 From One to Many Environments Configuration Plans Attached to the SOA archive file when deploying 28

29 From One to Many Environments 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) schemalocation attribute of an import in a WSDL file. locationattribute 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

30 From One to Many Environments Configuration Plans Replaces endpointsand locations inall referencesin all WSDL, XSD and JCA files <SOAConfigPlan.> <composite name="*"> <reference name="*"> <binding type="ws"> <property name="endpointuri"> <searchreplace> <search> </search> <replace> </replace> </searchreplace> </property> </binding> </reference> <reference name="*"> <binding type="ws"> <attribute name="location"> <searchreplace> <search> <replace> </replace> </searchreplace> : </composite> </SOAConfigPlan> 30

31 From One to Many Environments Configuration Plans Advantage Each composite can have a configuration plan for each environment (Development, Test, QA, Production, etc) 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

32 From One to Many Environments Global Token Variables 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 element. Only host, port, and protocol at the ws.bindinglocation 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

33 From One to Many Environments Global Token Variables mdm-url-resolver.xml <properties> <entry key="myprotocol">http</entry> <entry key="myhost">mymachine.us.example.com </entry> <entry key="myport">8001</entry> </properties> Composite.xml <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> </reference>... </composite> bpelprocess1_client_ep?wsdl 33

34 From One to Many Environments Global Token Variables 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 values. In a clustered environment, global token variable changes are made on the administration server and propagated to all managed servers. 34

35 Program Agenda From Design to Runtime From One to Many Environments Managing Deployed Composites Troubleshooting Additional Resources Q&A 35

36 Managing Deployed Composites 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 36

37 Managing Deployed Composites Redeploy Jdeveloper, ANT, WLST (deploy operation + overwrite) FMW Console (redeploy operation) 37

38 12c Managing Deployed Composites Redeploy If the deployed revision has instances in running, recovery or suspended state 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) 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

39 Managing Deployed Composites Redeploy Examples 12c 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 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

40 Managing Deployed Composites Undeploy JDeveloper, WLST, ANT and FMW Console Rules: 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 defaultrevision with noactive revision->retiredrevision becomes new default. Need to reactivate to process new messages. Can undeploy multiple SOA composites located in the same partition. 40

41 Program Agenda From Design to Runtime From One to Many Environments Managing Deployed Composites Troubleshooting Additional Resources Q&A 41

42 Troubleshooting Debug and Log Files Set following loggers to TRACE 32 in FMW Console: Oracle.soa.bpel.deployment Oracle.soa.bpel.compiler oracle.integration.platform.blocks.deploy Checkfor error messages in: DOMAIN_HOME/servers/<server-name>/logs/<server-name>.log DOMAIN_HOME/servers/<server-name>/logs/<server-name>-diagnostic.log 42

43 Troubleshooting Error Codes SOA Unable to find a WSDL that has a definition for service xxx SOA Unable to register service xxx.. Error in getting XML input stream 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

44 Troubleshooting Solutions My Oracle Support ( 44

45 Troubleshooting Solutions My Oracle Support 45

46 Troubleshooting Problem Configuration plan is not taking effect during deployment Cause 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

47 Troubleshooting Problem Cause Deployment cannot continue! No SOA Configured target servers found Used JDeveloperfor deployment and Admin Server is not running or is in 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

48 Troubleshooting Problem Cause oracle.fabric.common.fabricexception: Timed out waiting for operation to complete CompositeDeploymentCoordinatorMessages.throwTimedOutWaiting Coherence configuration is not correct. You maybe missing one or more of these parameters : tangosol.coherence.wka, tangosol.coherence.localhost, tangosol.coherence.localport) Solution OracleFusionMiddleware Enterprise Deployment Guide for Oracle SOA Suite 11g Release 1 ( ) 9.4 Configuring Oracle Coherence for Deploying Composites 48

49 Program Agenda From Design to Runtime From One to Many Environments Managing Deployed Composites Troubleshooting Additional Resources Q&A 49

50 Additional Resources Oracle Fusion Middleware Administrator's Guide for Oracle SOA Suite and Oracle Business Process Management Suite 11gRelease 1 ( ) and 12c (12.2.1) Oracle Fusion Middleware Developer's Guide for Oracle SOA Suite 11gRelease 1 ( ) and 12c (12.2.1) Deploying a SOA Composite Application Video (OLL YouTube Channel) Follow us on or SOA Proactive Blog 50

51 Q&A 51