SCA - The binding used for SCA invocations between modules.
SCA——用于模块间的SCA调用的绑定类型。
To communicate outside its SCA domain, whether to a non-SCA application or an SCA application running in some other SCA domain, a component must specify one or more bindings for this communication.
要在其sca域之外进行通信(无论是非sca应用程序，还是在其他sca域中的SCA应用程序)，组件都必须指定用于进行此通信的一个或多个绑定。
You explored how the SCA runtime creates the target application context for your SCA component.
您了解了SCA运行时如何为 SCA组件创建目标应用程序上下文。
If so, it needs to be exported using SCA export with SCA native binding.
如果是这样，则需要使用带sca本机绑定的sca导出将其导出。
SCA handles the infrastructure details for you.
SCA将为您处理基础结构细节。
We have just created an SCA component.
我们刚刚创建了一个SCA组件。
In this article, you learned how to integrate SCA solutions using SCA import and exports.
在本文中，您了解了如何使用SCA导入和导出集成sca解决方案。
Next, we will create SCA exports for each module so that the module can be invoked from other SCA modules.
接下来，我们将为每个模块创建sca导出，以便可以从其他SCA模块调用此模块。
SCA bindings enable SCA components in one module to communicate with SCA components in another module using the SCA programming model.
SCA绑定允许一个模块中的 SCA组件使用 SCA编程模型与另一个模块中的 SCA 组件通信。
SCA even has a specification for doing this.
SCA甚至有一个针对于此的规范。
As an SCA component within an SCA composite, it could do much more.
作为SCA组合中的SCA组件，它应该能够进行更多的工作。
The technique also works for SCA bindings.
这个技术也可以用于SCA绑定。
See Part 1 of this series for an overview of SCA bindings within the SCA assembly model.
有关SCA组装模型中的SCA绑定的概述，请参见本系列的第1部分。
SCA modules cannot be assembled from other modules.
SCA模块不能从其他的模块中收集到。
First, you need to create an SCA module.
首先，您需要创建一个SCA模块。
It transforms the request body into the SCA data object and passes the request data to other SCA application components.
它将请求体转换成sCA数据对象并将请求数据传递到其他SCA应用程序组件。
SCA modules contains SCA components or service components.
SCA模块包含 SCA组件或服务组件。
The required SCA reference injection would fail.
必需的SCA引用注入将失败。
Contributions are deployed into an SCA domain.
贡献包部署到某个sca域中。
The derived services can be referred to in other SCA components, just as with any other SCA service.
派生的服务可以在其他SCA组件中引用，就像其他任何 SCA服务一样。
Every SCA enabled server or cluster needs a Destination on the system SCA SI Bus for failed events.
每个启用sca的服务器或集群在系统scaSI总线上都需要一个用于失败事件的目的地。
As discussed in Part 1, SCA components are packaged into an SCA module.
正如第1部分所讨论的，SCA组件被打包成一个SCA模块。
An import with an SCA binding is a logical representation of an SCA component in another module.
使用SCA绑定的导入是SCA组件在另一个模块中的逻辑表示。
A client can get access to services from both SCA components and from non-SCA components.
客户机可以从SCA组件和非sca组件获得对服务的访问。
A domain consists of one or more cooperating SCA servers, or SCA runtimes, that host components in containers.
域包含了一个或多个协同操作的SCA服务器或者sca运行时，它们将组件托管于容器之中。
What is Service Component Architecture (SCA)?
什么是服务组件体系结构(SCA) ？
Figure 3 shows two SCA modules communicating with each other, and illustrates how an SCA import matches up with an SCA export.
图3显示了两个彼此进行通信的SCA模块，并说明了SCA导入如何与sca导出匹配。
SCA components can be invoked by non-SCA clients using exports.
非 SCA客户端可以通过导出调用SCA组件。
First, we will define the SCA component.
首先，我们要定义sca组件。
We will now define our SCA component.
现在我们要定义sca组件。
应用推荐