This procedure describes how to create an SCA project.
This section describes how an SCA project is created and used in the context
of creating your business service model. The description is numerically formatted
to clearly show the linear sequence of events.
The following assumptions apply for this discussion:
- A studio project has been created.
- A WID project is created.
- The business scenario is one in which you need to implement a business
service using SCA.
- This is a high-level description. It is assumed the reader understands
how to perform the actions defined in this discussion.
- In the Business Service perspective, create an application suite
- Create an application for the suite you created above.
- Setup a process service. You need to establish roles for the process service.
- Once you have created your roles for the process service, you must add
a channel and define it. For example you may want to make this service available
as a web service by implementing a web service channel to the process service.
- Open the Business Integration perspective.
- Open the Assembly Diagram. It is from this view that you will link your
services, setting up all endpoints and interfaces to services to create the
appropriate process flow.
Note: Depending on how the component in your flow
is defined determines what the service user sees versus what is going on in
the background. Also note that the components can have varying bindings such
as an SCA - interface. The SCA approach can dynamically assign components
and endpoints as needed, based on meta data in the repository versus having
each component hard wired to each other.
- Create your assembly diagram. At appropriate points, add a dynamic assembler
component to the flow. This enables the system to dynamically choose the correct
endpoint based on meta data stored in the repository.
- Assuming that your endpoints will also be SCA components, create separate
components for each one, but do not try to wire them to the dynamic assembler.
- Make sure that each component has the appropriate interface, then put
an Export in front each one.
- Wire each Export to its matching component.
- Right-click on each Export and choose “Generate Binding -> SCA Binding.
- After all Exports are created and configured, save your Assembly Diagram.
- Once all the above has been completed you need to test your model in the
Composition Studio module in order to understand what the interfaces are and
how the components function inside the process you have constructed.
- Switch to the Business Service perspective.
- Import the SCA modules from the Assembly Diagram as a composite service
into your Fabric Project. Do this by right-clicking on Endpoints, choosing
New -> Composite Service, then in the pop-up window make sure that the project
which contains your SCA components is selected.
- When you expand the Endpoint tree on the left side of your screen, you
should see an endpoint for each Export you created in your Assembly Diagram.
The result is also shown in the repository changes window on the right hand
side of your work space.
- Double click each endpoint, verify that the Protocol is SCA, and then
specify an Environment. Save each as you are finished to make the warnings
disappear.
- (Optional) If you want to test your services now, publish your changes
to the Business Services Repository. After they are approved, update your
project (right-click on your project in the Repository Changes window on the
right side and choose Update Project. Now switch back to the Business Integration
perspective and use the Test Component feature for each of your Dynamic Assemblers
to ensure that they work. When you are finished, switch back to the Business
Service perspective.
- Develop a policy for your service.
- In order to test your assumptions, test the policy by running the Dynamic
Assembly Simulator.
- Once you have verified your policy is operative, publish by submitting
your changes to the Business Services Repository.