44 SOA Solutions Using IBM Information Server
CREATE PROCEDURE DB2ADMIN.CCA_ADDCARDDETAILS SOURCE CCA.CCA_ADDCARDDETAILS FOR SERVER
2.6 Step 2: Identify and create “core” information
After the federation database has been prepared on the federation server, you
should create any DataStage jobs, QualityStage jobs, federated queries, and
stored procedures that you would like IBM Information Server to create SOA
In our A2Z Financial Services self service scenario, we had to create DataStage
jobs, QualityStage jobs, federated queries, and stored procedures as described
in the following sections.
2.6.1 Create DataStage and QualityStage jobs
Attention: For both DataStage and QualityStage jobs that you want to enable
as information services, you need to check the box Enabled for Information
Services. Right-click the StandardizeAddress job, and select Properties as
shown in Figure 2-4. Check the box, Allow Multiple Instance, which then
allows you to check the box, Enabled for Information Services, as shown in
Figure 2-5. Click OK.
Chapter 2. Financial services business scenario 45
Figure 2-4 Enable DataStage/QualityStage jobs as an information service 1/2
46 SOA Solutions Using IBM Information Server
Figure 2-5 Enable DataStage/QualityStage jobs as an information service 2/2
To implement the self service functionality, we defined the need for two functions
An audit trail function to record all actions taken by the customer. This
function can be delivered using DataStage capabilities and exposed as an
information service called AuditService. It is used by a number of self service
business functions such as performing a trade and opening a brokerage
account as described in “Step 5: Create “services” consumers” on page 307.
Implement a new standardization function for addresses entered by the
customer. This function can be delivered using QualityStage capabilities and
exposed as an information service called StandardizeAddressService. It is
used by a number of self service business functions such as opening a
brokerage account and updating credit card customer information as
described in “Step 5: Create “services” consumers” on page 307.
These are briefly described here.
Note: It is not our objective to explain the flows shown here. We assume that
you are familiar with DataStage and QualityStage functionality and flows.
Chapter 2. Financial services business scenario 47
Audit DataStage job
Figure 2-6 on page 48 through Figure 2-17 on page 54 show the DataStage flow
we designed for the audit trail function.
Figure 2-6 shows the overall flow of the function,
Figure 2-7 through Figure 2-9 on page 49 show the properties of the WISD_Input
Figure 2-10 on page 50 through Figure 2-11 on page 51 show the properties of
the Transformer stage.
Figure 2-12 on page 52 shows the properties of the WISD_Output stage.
In Figure 2-13 on page 52, we returned the application key (AppKey) as an
output of the Audit trail job — we are not interested in the returned value, but
must ensure that the WISD_Output stage job is not empty for the restriction
described in “Client application access to services” on page 18.
Figure 2-14 on page 53 through Figure 2-17 on page 54 show the properties of
the Audit_File stage.
Note: As mentioned earlier, the invocation of an IBM Information Server SOA
service is synchronous, and requires a request/response model. If there is no
response received by the invoker of the service, the requester will wait until a
response is received from the service. To address this limitation, we needed to
have the audit trail function send a response back to the invoker even though
the normal semantics of an audit trail is to submit a request and not wait for
the action to complete. This is implemented via the WISD_Output stage in
48 SOA Solutions Using IBM Information Server
Figure 2-6 Audit trail DataStage flow 1/12
Figure 2-7 Audit trail DataStage flow 2/12