Chapter 7. Scenario: Data transformation and security 189
The BankVerifyCredit operation is a one-way operation. The input to the
operation is the VerifyCreditType business object (Figure 7-11 on page 184).
The BankOpenAccount operation is a request-response operation. It has three
input/output types. The OpenAccountType business object is the input message,
the ackOAType business object is the output message, and the submitFaultType
business object is the fault message.
7.5.3 Business process
Figure 7-17 shows the LoanProcess business process.
Figure 7-17 Loan business process
The properties for this process are the default properties.
WSDL files: Interfaces are actual WSDL files. The WSDL file name usually
reflects the interface name. For example, the file name for LoanPrcInterface is
LoanPrcInterface.wsdl. However, in our example, the file name for the
BankPortType interface is actually
bank.wsdl. We highlight this fact, because
later you will see this file name used.
190 Using IBM WebSphere Message Broker as an ESB with WebSphere Process Server
Interface and partner references
The business process uses one interface partner and one reference partner. You
can see these listed to the right of the business process in Figure 7-17 on
page 189.
An
interface partner is the process interface and exposes operations that can be
called by external partners. The LoanPrcInterface interface is defined as an
interface partner for the interaction between the business process and its clients.
Reference partners specify the interface that is used in the invocation of another
service. In this scenario, two partner references are defined, one for each
message flow to be executed in WebSphere Message Broker:
? BankPortTypePartner (Figure 7-18) specifies that the BankPortType interface
is to be used to call the service. In the assembly diagram, this reference
partner is wired to the VerifyCredit import component.
Figure 7-18 Business process reference
Chapter 7. Scenario: Data transformation and security 191
? BankPortTypePartner1 (Figure 7-19) also uses the BankPortType interface to
call the service. However, in this case, the reference partner is wired to the
OpenAccountImport.
Figure 7-19 Business process reference
Receive activity
The Receive activity (Figure 7-20) receives the business process input from an
external client. It is associated with the LoanPrcInterface interface.
Figure 7-20 Receive activity configuration
ConfigSSLEnvironment Java Snippet activity
The interface that is used by LoanProcess to connect to the message flows in
WebSphere Message Broker is bound by using an HTTP secure channel. Most
of the HTTPS configuration is done at the application server level, but a few
configuration steps are required at the business process level.
192 Using IBM WebSphere Message Broker as an ESB with WebSphere Process Server
Before an import can make an external call, a few runtime properties must be
defined to the application JRE environment. Those variables can be defined as
entry values during the application server initialization (-D properties), or directly
with Java code.
In this scenario, before the bound ports can be executed on an external HTTPS
service call, a Java snippet activity (Figure 7-21) with the SSL configuration is
defined. This activity is added just after the Receive activity call and before an
import can be executed.
Figure 7-21 Java snippet used to set the SSL properties into the JRE environment
This Java snippet code defines the required SSL properties to use HTTPS
(Example 7-9).
Example 7-9 JRE SSL environment configuration
...
System.setProperty("javax.net.ssl.keyStore", <<keystore path>>);
System.setProperty("javax.net.ssl.keyStorePassword",<<password>>);
System.setProperty("javax.net.ssl.trustStorePassword",<<password>>);
System.setProperty("javax.net.ssl.trustStore", <<truststore path>>);
...
Keystore and truststore file system definitions: The file system definitions
for the keystore and truststore must reflect the same stores that are both used
in the WebSphere application server as in the WebSphere Message Broker.
Chapter 7. Scenario: Data transformation and security 193
VerifyCreditInvoke Invoke activity
The VerifyCreditInvoke Invoke activity (Figure 7-22) is associated with the
BankPortTypePartner partner reference. It uses the BankPortType interface to
send an HTTPS request to the WebSphere Message Broker.
Figure 7-22 VerifyCredit Invoke activity
Snippet activity
The Snippet Java snippet activity (Figure 7-23) is used to generate the content
that is expected by the OpenAccount business object.
Figure 7-23 Dynamic generating content for the OpenAccount business object
..................Content has been hidden....................
You can't read the all page of ebook, please click here login for view all page.