For users of both, MFT and SOA-Suite, both can be integrated. The SOA Suite can push data to MFT, which takes care of distributing those in the file system. And vice versa, the SOA Suite can be a target for a MFT transaction.
For this example, both MFT and SOA Suite should be installed. Basic knowledge of both products is required.
Starting with the Design tab of the MFT Console. A new source of type SOA is created here. Important: don't chose the name soa as depicted above, as this will lead to problems later. So chose a different name like service-source.
Next, a Transfer needs to be created, using the newly created service-source as Source. Create any File Target as target for this transformation, eg. the file-target from chapter 3.
Then click Save and Deploy, so both artifacts are deployed.
Next, open JDeveloper and create a new SOA-Project.
In the composite, drop a MFT adapter to the right side.
Accept the defaults
Also keep the defaults here
In this step, an existing application server connection can be chosen or a new one be created. The MFT server in that domain will be found automatically, click on Test MFT to check the connection.
The serivce-source will be found automaticall, end this wizard with Finish.
To have something to communicate with the MFT adapter, drop a BPEL process into the composite. In the dialog shown above, switch it to Synchronous BPEL Process and leave the rest.
Connect the MFT adapter with the BPEL process, then open the process with a double click.
Place an Invoke activity in the middle and connect it with the MFT partner link.
Create an input- and output-variable by clicking on each green plus sign (+). Then close the dialog with OK.
An assign activity is needed, place it before the Invoke1 and open it via double click.
Right click on ns1:InlinePayload to assign an expression.
Create a greeting, eg. one matching the region you live in. In my case:
concat("Moin, Moin ", $inputVariable.payload/client:input)
Do the same for ns1:TargetFilename. As this is the name for the target file, better avoid special characters which could cause troubles on some file systems. Eg.:
concat("Hello-",$inputVariable.payload/client:input)
The composite is ready now and need to be deployed (right click on [project name]|Deploy).
Next, open the Enterprise Manager and navigate to that project. Go to the Test Web Service page, enter a test string and start the test.
If everything was OK, the Flow Trace can be launched.
The flow trace will contain a MFT step, click on it.
This will lead to the MFT Console where the Transfer will be displayed.
In the file system, the resulting will be created. Open it and check the contents.
That's the end of the MFT tutorial
