Use the administrative console in IBM® Business Process Manager to view and change aspects of service applications and service modules.
Service applications provide services, and have an associated service module, also called a Service Component Architecture (SCA) module.
Viewable module details
After you have deployed an enterprise archive (EAR) file containing an SCA module, you can view SCA module details. You can list all your SCA modules, and their associated applications, and you can view details about a particular SCA module.
You can view the following SCA module details:
- SCA module name
- Associated application
- SCA module imports:
- Interfaces
- Bindings
- SCA module exports:
- Interfaces
- Bindings
- SCA module properties
Modifiable module details
After you have
deployed an EAR file containing an SCA module you can use the administrative
console to change the following SCA module details. You do not need
to redeploy the EAR file.
Important: Some
SCA modules are associated with a process application; they provide
the service integration functionality for that process application.
If an SCA module is associated with a process application, do not
use the administrative console to manage its state. Instead, use the
Process Admin Console. The state of any SCA module in a process application
is managed as part of the overall process application state within
the Process Admin Console.
- Import bindings of type SCA:
- Import bindings define service interactions. You can change the bindings if you want to change the service interactions.
- SCA bindings connect SCA modules to other SCA modules. One SCA module can interact with a second SCA module, and can be changed to interact with another SCA module.
- Web service bindings connect SCA modules to external services using SOAP.
- Import bindings of type Web service (WS):
- Import bindings define service interactions. You can change the bindings if you want to change the service interactions.
- SCA modules use WS import bindings to access web services. A WS import binding calls a service located at a specified endpoint. You can change the end point so that the binding calls the service at an alternative end point, or calls an entirely different service with compatible interfaces.
- Export and import bindings of types JMS, WebSphere MQ JMS, generic JMS, WebSphere MQ, and HTTP have attributes that you can modify.
- Mediation module properties:
- Mediation module properties belong to the mediation primitives with which they are associated. However, the administrative console displays some of them as Additional Properties of an SCA module. The integration developer must flag a mediation primitive property as Promoted in order for it to be visible.
- Mediation module properties affect the behavior of your mediations. The mediation changes that you can make depend upon the properties that have been promoted.
Important: An export with no binding specified
is interpreted by the run time as an export with an SCA binding.
Figure 1. Example showing one mediation
module interacting with another mediation module. Mediation
Module1 connects to Mediation Module2