Component Assembly and Configuration
Create module imports, exports and standalone references
Imports
An import allows you to use functions that are not a part of the module that you are assembling.
Imports are used in an application in exactly the same way as local components. This consistency provides a uniform assembly model for all functions, regardless of their locations or implementations.
Imports have interfaces that are the same as, or a subset of, the interfaces of the remote service that they are associated with so that those remote services can be called. To share the interfaces between modules, put the interfaces into a library. Then, for both modules, add a dependency on the library to use its resources.
Imports and exports require binding information, which specifies the means of transporting the data from the modules. An import binding describes the specific way an external service is bound to an import component. For an import that is generated from an export, the binding type of the import will be specified for you. Imports can use the following bindings: SCA, Web service, HTTP, messaging (JMS, MQ JMS, generic JMS, MQ), stateless session bean, and EIS. Available function (or business logic) implemented in remote systems (such as Web services, EIS functions, EJBs, or remote SCA components) is modeled as an imported service.
Exports
An export is a published interface from a component or import that offers its service to the outside world, for example, as a Web service.
Exports have interfaces that are the same as or a subset of the interfaces of the component or import that they are associated with so that the published service can be called. An export dragged from another module into an assembly diagram will automatically create an import. Exports that are shown under the module assembly in the Business Integration view can also be used to create imports in other modules.
Each export has an address at which it will be deployed on the server. The export can be exposed at that address.
Imports and exports require binding information, which specifies the means of transporting the data from the modules. When you use the Generate Export action from the menu of a component, you need to select the binding so that the binding is generated when the export is created. An export binding describes the specific way a module's services are made available to clients. If an export in a module assembly does not have any binding, when deployed, SCA binding is assumed.
For enterprise information systems (EIS), an export allows an event in the enterprise system, such as the creation of a business object in SAP, to drive an action. Unlike other exports, you cannot drag and drop an export with an EIS binding to create an EIS import.
Exports have interfaces that are the same as or a subset of the interfaces of the component or import that they are associated with so that the published service can be called. An export dragged from another module into an assembly diagram will automatically create an import. Exports that are shown under the module assembly in the Business Integration view can also be used to create imports in other modules.
Each export has an address at which it will be deployed on the server. The export can be exposed at that address.
Imports and exports require binding information, which specifies the means of transporting the data from the modules. When you use the Generate Export action from the menu of a component, you need to select the binding so that the binding is generated when the export is created. An export binding describes the specific way a module's services are made available to clients. If an export in a module assembly does not have any binding, when deployed, SCA binding is assumed.
For enterprise information systems (EIS), an export allows an event in the enterprise system, such as the creation of a business object in SAP, to drive an action. Unlike other exports, you cannot drag and drop an export with an EIS binding to create an EIS import.
Stand-alone references
Stand-alone references allow a Java™ program to invoke SCA components or imports.
Services that are not defined as SCA components (for example, JavaServer Pages) can still invoke SCA components; they do so through the use of stand-alone references. Stand-alone references contain partner references that identify the components to call. On their own, stand-alone references do not have any implementation or interface.
You can use the palette in the assembly editor to create stand-alone references in the module assembly. You can add partner references to the stand-alone references and wire them to target components or target imports.
Services that are not defined as SCA components (for example, JavaServer Pages) can still invoke SCA components; they do so through the use of stand-alone references. Stand-alone references contain partner references that identify the components to call. On their own, stand-alone references do not have any implementation or interface.
You can use the palette in the assembly editor to create stand-alone references in the module assembly. You can add partner references to the stand-alone references and wire them to target components or target imports.
Note: You can only use one stand-alone references node in each assembly diagram.
No comments:
Post a Comment