This procedure describes how to create a System Component Architecture
(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 WebSphere Integration Developer 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.
To create an SCA project, complete the following steps:
- In the Business Service perspective, create an application suite
- Create an application for the suite you created above.
- Set up 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 each Export, and click .
- 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 endpoints, and then clicking .
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 Pprotocol is SCA, and then
specify an environment. Save each as you are finished to make the warnings
disappear.
- 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 your project in the Repository Changes window on
the right side, and select 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 it by
submitting your changes to the Business Services Repository.