(System MBean Browser) Change the remote FTP path from em console @ runtime

In the composite, logical properties are specified in the inbound JCA file and their logical-physical mapping is resolved by using binding properties.

This gives you the below flexibility:

You specify the logical parameters once at design time, and you can later modify the physical directory name as needed.



In the design view of composite, you can select the exposed FTP Service and add the properties to specify the actual path for Logical directory paths.

Design view – composite.xml

Source view – composite.xml

soa-infra > System MBean Browser >Application Defined MBeans

Use the below filter expression to rightly oracle.soa.config:name=your service name



Under Attributes of selected MBean choose Properties and find properties specifies in composite as under Key

These details say- directory path can be can be re-configured and the changes can be applied at run-time.

(Secured FTP) POLL and ARCHIVE file using BPEL 11g

Problem statement:

- I would like to poll a file from a directory structure -/tmp/SAPI093 within a secured FTP location.,

- Upon successful polling I would like to archive the same on different directory path -/tmp/SAPI093/archive



ISSUE : After successful creation of jca adapter for Secured FTP ,I am able to get the polled file deleted from source directory but, failed in archiving of polled file in archive directory in the Source FTP location .

Solution: To fix the same you will need to add the binding property “UseRemoteArchive” to true.

Design view – composite.xml

Source view – composite.xml

In the composite, logical properties are specified in the inbound JCA file and their logical-physical mapping is resolved by using binding properties.

You specify the logical parameters once at design time, and you can later modify the physical directory name as needed.



In the design view of composite, you can select the exposed FTP Service and add the properties to specify the actual path for Logical directory paths.

Design view – composite.xml

Source view – composite.xml

BPEL Component as a REST SERVICE(using HTTP Adapter)

BPEL Component as  a REST SERVICE(using HTTP Adapter)

 

Task: To expose a SOA Component (a BPEL Service Here ) as a REST (HTTP based) service using HTTP Binding Adapter

• Open A new Empty SOA Project.


• Go to Composite.xml->Drop the HTTPBinding Adapter  from component pallet @ the left to to the Exposed Services Swimlane at the LeftHandSide

• Follow the below screen shot to configure & complete the HTTP Binding Wizard.


• 
  
  You may use any schema for configuring the request and response Message structure withing the HTTPBinding .
  
  
   
  
  
  BPELProcess1.xsd
  
  
   
  
  
  <?xml version="1.0" encoding="UTF-8"?>
  
  
  <schema attributeFormDefault="unqualified"
  
  
      elementFormDefault="qualified"
  
  
      targetNamespace="http://xmlns.oracle.com/Application1/Project1/BPELProcess1"
  
  
      xmlns="http://www.w3.org/2001/XMLSchema">
  
  
      <element name="process">
  
  
          <complexType>
  
  
              <sequence>
  
  
                  <element name="input" type="string"/>
  
  
              </sequence>
  
  
          </complexType>
  
  
      </element>
  
  
      <element name="processResponse">
  
  
          <complexType>
  
  
              <sequence>
  
  
                  <element name="result" type="string"/>
  
  
              </sequence>
  
  
          </complexType>
  
  
      </element>
  
  
  </schema>
  
  
  
  

  
  
  • Step 1,Step2 and Step3 for HTTP Binding Wizard
  
  

  
  

 

 

 

• Note:In HTTP Binding wizard Step 4:Verb and Payload-Type can be manipulated by manually edited in the composite.xml later and

 

 

 

Once The Adapter is configure for being exposed as a service.,

• Drop an empty BPEL Process in the component area.


• Open the BPEL and complete the desired flow using a receive and reply activity witha desired transformation between these .

 

 

To make available all the HTTP Methods for the service both GET and POST , composite so that HTTP Bindings comes with its default behavior remove the properties that appear in composite

 

So that once deployed the composite , you have the blow shown methods available for invocation.