WID 6012.9 Export/Import SCA Binding How to

WID V6.0.1.2, Interim Fix 009

How to import a component using Web Services Binding

A Completed Web Service Import Binding This is the completed import nodes using various import bindings. You use imports to invoke external services. The following steps describes in details how to setup a web service import binding.
Select the Web Service Port Drag the web service port from the library to the Assembly Diagram.
Select Import with Web Services Binding and click OK.
An import is created. Change the name from Import1 to DateTime_CImport_ WS Wire the component (i.e Consumer) to the Web service import Save the module
Fix Synchronization errors When you change a component, i.e, adding or deleting interfaces/references, you have to synchronize the changes to the component's implementation. To fix this error, right-click the component and select Synchronize Interfaces and References > to implementation.
Web Services Import Generated Artifacts Web Service import binding generates the following artifacts: Dynamic Web Project (Consumer...). Web ServicesClients (Consumer...)

How to export a component using Web Services Binding

A Completed Web Service Export Binding

This is the completed export nodes using various export bindings.

You use exports to make your services available to other components in external modules.

The following steps describes in details how to setup a web service export binding.

Right click the component you want to export and select Generate Export... > Web Services Binding.

Click Yes.

Select soap/http as the transport and click OK.

Rename WS export node

An export node (DateTime_CExport) and a Web Service Port are created.

Rename DateTime_CExport to DateTime_CExport_WS.

Do this by the export node name and appending _WS to it.

Important:

If you re-name the ws export node, you must also rename the related Web Service Port. Otherwise, you will get a 404 error (not found).

After Rename

Rename WEB Service Port

Ensure that the web service export node name(i.e, DateTime_CExport_WS in this example) is the same as the last block in the Web Service Port name.

To rename the Web Service Port name, do the following:

Double-click the Web Service Port name (i.e DateTime_CExport....).
Expand Services
Click soap:address
Rename the last block of location:Value to the Web service export node name.
Save project

From

http://localhost:9080/CCambil_Provider_MWeb/sca/DateTime_CExport

http://localhost:9080/CCambil_Provider_MWeb/sca/DateTime_CExport_WS

Test the Web Service Export binding.

Right-click the Web Service export node you want to test and select Test Component.

Follow the same procedure specified in testing an exported component.

Share the Web Service Port

Sharing the Web Service port enables external modules to invoke your web service.

Steps:

Right-click the Web Service port you want to share and select Copy.
Right-click the library you want to copy the port to and select Paste.
The port is copied into the library.

Web Service Export Generated artifacts

The following artifacts are generated when you define a web service export binding:

Web Service Port
Dynamic Web Project

Dynamic Web Project

Web Service Port

JMS resources generated by Websphere Integration Developer

Resources are generated by default by WID 6.0.1.2 when you select Configure new messaging provider resources during the configuration of JMS Export Service. We will look at the following resources (CCambil) generated by WID: Resources > JMS Providers > Default messaging Buses" href="http://www.blogger.com/RawDocContents?docID=dhr7zgxb_708hh27k3dc&justBody=false&revision=_latest&timestamp=1212589257016&editMode=true&strip=true#Service_Integration_-_Buses">Service integration > Buses
Default Messaging Provider A JMS provider enables messaging based on the Java Messaging Service (JMS). It provides J2EE connection factories to create connections for JMS destinations. This panel is used to manage the default messaging provider and its JMS resources. Select Server : Server1 and click Apply. We will look at the following resources: JMS connection factory JMS queue JMS activation specification
JMS connection factory A JMS connection factory is used to create connections to the associated JMS provider of JMS destinations, for both point-to-point and publish/subscribe messaging. Use connection factory administrative objects to manage JMS connection factories for the default messaging provider.
JMS Queue A JMS queue is used as a destination for point-to-point messaging. Use JMS queue destination administrative objects to manage JMS queues for the default messaging provider.
JMS activation specification A JMS activation specification is associated with one or more message-driven beans and provides the configuration necessary for them to receive messages.
Service Integration - Buses A service integration bus supports applications using message-based and service-oriented architectures. A bus is a group of interconnected servers and clusters that have been added as members of the bus. Applications connect to a bus at one of the messaging engines associated with its bus members. Click on SCA.APPLICATION.widCell.Bus to display messaging bus for Service.
SCA.APPLICATION.widCell.Bus A service integration bus supports applications using message-based and service-oriented architectures. A bus is a group of interconnected servers and clusters that have been added as members of the bus. Applications connect to a bus at one of the messaging engines associated with its bus members. Click on Destinations to display destinations.
Destinations A bus destination is a virtual place, within a service integration bus, to which applications attach as producers, consumers, or both to exchange messages.

How to export a component using JMS Binding

This is the completed export nodes using various export bindings. You use exports to make your services available to other components in external modules.
Right-click the component you want to export and select Generate Export > JMS Binding.
Select Configure new messaging provider resources to automatically define Server resources during project deployment (i.e, Websphere Integration Developer 6.01.2 will define the server resources when you initially deploy the project). Set the Serialization type to JMS TextMessage
WID automatically defined the following JMS export settings. The following resources will be setup by default when you deploy the project to the Server.

How to import a component using JMS Binding

This is the completed import node using JMS bindings. You use imports to invoke another component located in another module.
Drag the service (Export node) from the other module (i.e, the ServiceProvider module) and drag it to the module (i.e ServiceConsumer module) that wants to use it.
This is an informational message. Note: Deploy the external module first before deploying the invoking module. Click OK to continue.
WID automatically defined the following JMS import settings. Review and compare the Export/Import settings automatically defined by WID 6012.	Export Import

How to test an exported component

The primary reason for testing the Export node is to ensure that the Export binding works before being used by other modules. Right-click the Export node and select Test Component.
Review and configure the Detailed Properties values to ensure that the test is properly setup.
Remove all Emulators so that the actual components that you are building will be used during testing.
Select Deployment Location.
Review test results.

How to test an imported component

The primary reason for testing the Import node is to ensure that the Import binding works before using other modules.

Right-click the Import node and select Test Component.

Follow the same procedure specified in testing an exported component.

How to Import a component using SCA Binding

Create an import to use an existing service that is not part of the module that you are assembling (it is in another module). Drag the service (Export node) from the other module (i.e, the ServiceProvider module) and drag it to the module (i.e ServiceConsumer module) that wants to use it.
Select no Binding or SCA Binding depending on your requirements and click OK.
An Import node with SCA binding is created. Rename the Import node as required.
Wire the module to the Import node.
Click OK when this confirmation is displayed.
The ServiceConsumer component can now invoke another component in another module through the Import node.