Table of Contents

Search

  1. Preface
  2. Introduction
  3. Servers
  4. Console Client
  5. Search Clients
  6. Table Loader
  7. Update Synchronizer
  8. Globalization
  9. Siebel Connector
  10. Web Services
  11. ASM Workbench
  12. System Backup and Restore
  13. Batch Utilities

Deploying a Real-Time Web Service

Deploying a Real-Time Web Service

This section outlines the steps required to establish a Real-Time Web Service in an IIR environment.

Prerequisites

The Synchronization Server must be running and the Real-Time Web Service must be configured. See the
Enabling the Real Time Web Service
section for further details.

WSDL

WSDL files are created by the Synchronization Server in the server work directory for each rule and system defined in the
xrserv.xml
file when the server starts or is refreshed. The WSDL can also be accessed through the server at:
http://<xshost>:<xsport>/?<system>.wsdl
where
<system>
is the last-mentioned system in the
xrserv.xml
file. For example, the
ssa003
sample system will usually be found at:
http://localhost:1670/?testx345.wsdl
The WSDL can also be retrieved from :
http://<xshost>:<xsport>/?<rule>.wsdl

Re-generating the WSDL file

The WSDL file can be regenerated by issuing a flush command to the server. The server will re-read the
xrserv.xml
file and re-create the WSDL file. For example, on Windows:
%SSABIN%\ssashut -h%SSA_XSHOST% -f
Or on Unix:
$SSABIN/ssashut -h$SSA_XSHOST -f

Creating a .NET Proxy

One can create a C# .NET proxy with the supplied
compile.bat
script in the csharp-xml directory. You must have Microsoft Web Service Extensions (WSE) 3.0 installed. The script accepts an argument that instructs it to use WSE 3.0. This is required by
ws-sample6.cs
, so compile with:
compile wse3
The first step is to build the proxy:
%ProgramFiles%\Microsoft WSE\v3.0\Tools\WseWsdl3.exe /out:ssa003.cs ssa003.wsdl
This can be then be compiled with:
csc /target:library /out:ssa003.dll ssa003.cs
and linked with a client program,
csc /target:exe /reference:ssa003.dll ws-sample6.cs
The main part of the
ws-sample6.cs
is:
ssa003 sync = new ssa003 (); if (null != xrserv) sync.Url = xrserv; int response = sync.IDT003 (AcctNo, Address, CL_ID, DOB, Name, IDS_OP, IDS_SEQ, out status, out messages); foreach (AuditMSG message in messages) { Console.WriteLine ("response={0}", response); Console.WriteLine ("status={0}", status); Console.WriteLine ("rulebase={0}", message.Rulebase); Console.WriteLine ("system={0}", message.System); Console.WriteLine ("IDT={0}", message.IDT); foreach (ClusterAction cluster_action in message.ClusterAction) { Console.WriteLine ("Type={0}", cluster_action.Type); Console.WriteLine ("ID={0}", cluster_action.To.ID); Console.WriteLine ("No={0}", cluster_action.To.No); } }
From this, we can see that
  • The sync class has the name of the IIR system.
  • The method
    sync.IDT345
    takes IDT input fields to be synchronized as parameters.

Extract from the SDF File

Section: User-Source-Tables * create_idt idt003 sourced_from flat_file (pk) AcctNo C(11), Name C(50), DOB C(8), Address C(40) SYNC REPLACE_DUPLICATE_PK TXN-SOURCE NSA

Layout of the IDT

Column
RECD
IDS_ACCTNO
IDS_NAME
IDS_STREET
IDS_ADDR4
IDS_CITY
IDS_STATE
IDS_ZIP
IDS_GEOALPHA
IDS_LASTNAMECHAR2
IDS_CL_ID
  • The response message includes TXN processing status, response, cluster-related information etc.
  • Errors are thrown as SOAPException exceptions.
  • WebException exceptions may be thrown. This will occur if an attempt is made to run the client without bringing the server up.

0 COMMENTS

We’d like to hear from you!