Industry Solutions
B2B and Commerce
WTX 8.4.1.1 Release Contents
Sunil Dandamudi – Architect, WebSphere Transformation Extender
sdandamu@us.ibm.com
© 2013 IBM Corporation
Industry Solutions
B2B and Commerce
Agenda
Release
• Details
• Contents
• Q& A
2
© 2013 IBM Corporation
Industry Solutions
B2B and Commerce
Productivity - PARSE
A Parse function allows to parse and validate a data stream and associate
the data structure with the a type structure on the LHS.
Syntax :
= PARSE (TEXT BLOB)
Return a parsed and validated data structure
3
© 2013 IBM Corporation
Industry Solutions
B2B and Commerce
Productivity - PARSE
 Reduced complexity while dealing with data retrieved through External
Functions (GET, RUN, DBQUERY) that needs to be parsed and mapped
 Improves performance where data objects are currently parsed multiple
times in parent/run maps
 Supports Data Audit on type objects
 Trace is available as part of corresponding output card trace
 Map fails with Error Code 27 , Output Type contains Errors
4
© 2013 IBM Corporation
Industry Solutions
B2B and Commerce
Productivity - PARSE
 Usage Pattern
= PARSE (TEXT BLOB)
= PARSE (TEXT BLOB) + RULE  Not Supported
= RULE + PARSE (TEXT BLOB)  Not Supported
5
© 2013 IBM Corporation
Industry Solutions
B2B and Commerce
Productivity - PARSE
Objects Populated with data
=PARSE(GET("SPE", "-DURL
jdbc:derby://localhost:1527/spe2;user=derbyuser;password=derbyuser DBDRIVER org.apache.derby.jdbc.ClientDriver -MAP parsewds TRANSFORM -T", Input))
6
© 2013 IBM Corporation
Industry Solutions
B2B and Commerce
Productivity - ASFUNCTION
Introducing ASFUNCTION Function
A “ASFUNCTION” function allows to behave a functional map as a
function in map rule
Syntax :
= ASFUNCTION(Function map)
Returns the data from the functional map as inline to the invoking map rule
7
© 2013 IBM Corporation
Industry Solutions
B2B and Commerce
Productivity - ASFUNCTION
Supported only when a functional map returns a Item
Concept has been introduced in 8.4.1 as a general functional map
behavior, but backed out due to mapping disruptions to our customers
Usage Patterns
= RULE + ASFUNCTION () + RULE
Reduces mapping complexity when dealing with data returned from a
functional map to be used as part of a rule
8
© 2013 IBM Corporation
Industry Solutions
B2B and Commerce
Productivity - XVALIDATE
Enhanced XVALIDATE function to support XML snippets
The XML document no longer need a Prolog to be validated through
XVALIDATE functions
9
© 2013 IBM Corporation
Industry Solutions
B2B and Commerce
Native XML – XSDL Hints
 Added Support for two new properties on
Native XML output card
– xsi:schemaLocation
– xsi:noNamespaceSchemaLocation
– The values specified for these
properties will appear in the root of
the xml document
– Refer to XML Specification for
more details on these properties
http://www.w3.org/TR/xmlschema1/#xsi_schemaLocation
10
© 2013 IBM Corporation
Industry Solutions
B2B and Commerce
Productivity – TEST DATA
Introduced Test Data Generation in Type Designer
Allows user to generate a test data for a specific group or item
Allows users to save the test data artifacts for further customization based
on the needs.
Generate test data for first choice and the first partitioned group
Allows users to generate test data for optional elements and adds default
data rules for items
11
© 2013 IBM Corporation
Industry Solutions
B2B and Commerce
Productivity – TEST DATA
Select a group or item and use Generate Test Data context menu
12
© 2013 IBM Corporation
Industry Solutions
B2B and Commerce
Adapter – SPE
 The Standards Processing Engine (SPE) adapter connects WTX with Standards Processing
Engine (SPE).
 System Requirement :
 The Standards Processing Engine (SPE) adapter function requires the installation of
Standards Processing Engine and a solution Pack
 Standards Processing Engine (SPE) adapter commands fall into two categories:

– Data harness functions
– Adapter action commands.
13
© 2013 IBM Corporation
Industry Solutions
B2B and Commerce
Adapter – SPE
Adapter Command Line for SPE connectivity
14
DBURL
Identifies the SPE database by either the database
URL or the file URL of a
configuration file that contains the database
connection information. If you
specify a configuration file, the SPE adapter uses
only the database
connection information in the configuration file. The
adapter ignores any
-DBDRIVER, -DBUSER, -DBPSWD, or DBSCHEMA keywords on the adapter
command line.
The -DBURL keyword is required
DBUSER
User Name
DBPSWD
User Passoword
DBDRIVER
Driver Name
DBSCHEMA
Specifies the name of the SPE database schema.
© 2013 IBM Corporation
Industry Solutions
B2B and Commerce
Adapter – SPE
Adapter Command Line options for SPE
15
Map
Specifies the name of the map in the SPE
database or, for WebSphere
Transformation Extender maps only, the file
URL of the map on the local
file system. The -MAP keyword is required
for TRANSFORM command
DOCID
Specifies the document ID of the document
in memory that overrides the first input card
of the map
KEEP
Retains the documents that are returned in the
SPE response by storing the
documents
ALLDOCS
Specifies that SPE is to return all documents in the
XML response file,
including type=INTERMEDIATE documents
BATCH
Specifies the document ID of a single document to
de-envelope
© 2013 IBM Corporation
Industry Solutions
B2B and Commerce
Adapter – SPE
Adapter Command Line options for SPE
16
SENDER
Specifies the document sender that is used to
locate the envelope
information in the SPE database.
RECEIVER
Specifies the document receiver that is used to
locate the envelope
information in the SPE database
ALIAS
Specifies the acceptor look-up alias to locate the
envelope information in
the SPE database.
© 2013 IBM Corporation
Industry Solutions
B2B and Commerce
Adapter – SPE
Data harness functions read and write to the underlying SPE database
through a data harness, and are valid only when a map is running under
SPE.
17
GetBinaryDocument
Retrieves the specified binary
document. This command is valid in a
GET
function.
getEnvelope
Retrieves the specified field from an
envelope. This command is valid in a
GET function.
© 2013 IBM Corporation
Industry Solutions
B2B and Commerce
Adapter – SPE
setCorrelation
Updates the Standards Processing
Engine correlation table with the
specified name/value pair for the
document.
getProcessData
Retrieves process data from the XML
document object model (DOM)
specified by the XPath
setProcessData
Stores process data from the current field
into the XML DOM that is
specified by the XPath
18
© 2013 IBM Corporation
Industry Solutions
B2B and Commerce
Adapter – SPE
getCodeListItemBySenderCode
Retrieves a trading-partner code-list
entry from SPE by sender code.
getCodeListItemByReceiverCode
Retrieves process data from the
XML document object model (DOM)
specified by the XPath
getTransactionRegister
Compares the fields that you loaded
into the Transaction Register with
the
input data, returns a code, and
clears the Transaction Register
19
© 2013 IBM Corporation
Industry Solutions
B2B and Commerce
Adapter – SPE
setTransactionRegister
Gets a delimiter from an SPE
document envelope. This command
is valid
in a GET function..
validateCodeWords
Validates a series of code words
defined by a delimited string
20
© 2013 IBM Corporation
Industry Solutions
B2B and Commerce
Adapter – SPE
Adapter action commands are valid in maps that are running on WTX
Launcher, Command Server, or the TX Programming
Interface
ADOC
The -ADOC command adds one or more
files on the file system as a document in
memory and returns the document ID to
the map
GDOC
The -GDOC command returns data from
a document in memory or file system
based on the document ID
21
© 2013 IBM Corporation
Industry Solutions
B2B and Commerce
Adapter – SPE
ADOC
The -ADOC command adds one or more
files on the file system as a document in
memory and returns the document ID to
the map
UDOC
The -UDOC command replaces an
existing document in memory with a new
one
and returns the new document ID.
RDOC
The -RDOC command removes one or
more documents from memory. By
default,
documents are removed from memory
when map processing completes.
22
© 2013 IBM Corporation
Industry Solutions
B2B and Commerce
Adapter – SPE
TRANSFORM
The -TRANSFORM (-TFM) command
runs a map on the Standards Processing
Engine (SPE) and returns a response
from SPE in XML format. The TRANSFORM command can run a
WebSphere Transformation Extender
map, a Sterling B2B Integrator map,
or an XSLT map.
De-Envelope
The -DEENVELOPE (-DENV) command
de-envelopes a document as specified in
the Standards Processing Engine (SPE)
database and returns a response from
SPE in XML format
23
© 2013 IBM Corporation
Industry Solutions
B2B and Commerce
Adapter – SPE
Envelope
24
The -ENVELOPE (-ENV) command
envelopes a document as specified in the
Standards Processing Engine (SPE)
database and returns a response from
SPE in XML format
© 2013 IBM Corporation
Industry Solutions
B2B and Commerce
Adapter – SPE
 The Adapter commands returns a XML response file contains the document IDs
of the enveloped documents.
 The metadata schema of the XML response is defined by the
wtx_install_dir\Response.xsd file.
 Users needs to map the Response file to a Output card and use the SPE adapter
to process the data
 WTX SPE Adapter documentation has a details lay out of the functions and their
parameters
25
© 2013 IBM Corporation
Industry Solutions
B2B and Commerce
Adapter – SPE (Response Message)
Status
Status Message returned by SPE
Advanced Status
Advanced Status message returned by
SPE
Report
Return Translation Report from SPE
Process Parameters
process parameters - similar to Process
Data name/value data
Version
Version number of the Response
Schema
Transform Correlation
Gets the correlation object instances
associated with transformations for a
specific objectID
Documents
SPE Documents are returned as DOC ID
to the map
Correlations
A list containing the correlations returned
by SPE
26
© 2013 IBM Corporation
Industry Solutions
B2B and Commerce
Adapter – SPE (DE-Envelope)
Add Card
(Response Schema as Root)
Invoke SPE Adapter
(Card Adapter, GET)
Wrap GET with PARSE
Based on Response Status, Retrieve each document by
using SPE adapter with GDOC command. The Document
IDs are part of the Response object on the card
27
© 2013 IBM Corporation
Industry Solutions
B2B and Commerce
Adapter – SPE (Transform)
Add Card
(Response Schema as Root)
Invoke SPE Adapter
(Card Adapter, GET)
Wrap GET with PARSE
Based on Response Status, Retrieve the document by
using SPE adapter with GDOC command. The Document
ID is part of the Response object on the card
Note : WTX map overrides first input card and last output card as part of
Transform
28
© 2013 IBM Corporation
Industry Solutions
B2B and Commerce
Adapter – SPE (Envelope)
Add Card
(Response Schema as Root)
Invoke SPE Adapter
(Card Adapter, GET)
Wrap GET with PARSE
Based on Response Status, Retrieve each document by
using SPE adapter with GDOC command. The Document
IDs are part of the Response object on the card
29
© 2013 IBM Corporation
Industry Solutions
B2B and Commerce
Adapter – SPE Snapshot
=PARSE(GET("SPE", "-DURL
jdbc:derby://localhost:1527/spe
2;user=derbyuser;password=de
rbyuser -DBDRIVER
org.apache.derby.jdbc.ClientDri
ver -MAP parsewds TRANSFORM -T", Input))
30
© 2013 IBM Corporation
Industry Solutions
B2B and Commerce
SPE – Design Studio
 Enhanced Design Studio to integrate with
Standards Processing Engine
– XSLT, Sterling and WTX map can be
checked in to SPE Database
– XSLT, Sterling and WTX map can be
tested on SPE Engine
New Category
– Allows to configure multiple databases to
test SPE on. This simplifies on-boarding
multiple SPE environments (Test,
Development and Production) with ease
31
© 2013 IBM Corporation
Industry Solutions
B2B and Commerce
SPE – Design Studio (Preferences)
 SPE added to Design Studio Preferences
– Available only when SPE is installed
– Available with WTX Design Studio
– Allows to configure database settings,
Deployment , Test and Logging Options
New Preference for SPE
32
© 2013 IBM Corporation
Industry Solutions
B2B and Commerce
SPE – Design Studio (Preferences - Connectivity)
 Allows to Define SPE Database
Connectivity information
– Multiple Database connections
can be setup for each user
environment
33
© 2013 IBM Corporation
Industry Solutions
B2B and Commerce
SPE – Design Studio (Preferences)
 Deploy
– Default comments
for check-ins
– Unique Reference
Identifier
 Test
– Default Input/Output
files generated for
SI and XSLT
– WTX Resource
Registry
Configuration
 Logging
– Session Logs
– Log Levels
34
© 2013 IBM Corporation
Industry Solutions
B2B and Commerce
SPE – Design Studio
 Allows to Check-in
– XSLT
– Sterling
– WTX
 Allow to Test maps
inline on SPE engine
– XSLT
– Sterling
– WTX
35
© 2013 IBM Corporation
Industry Solutions
B2B and Commerce
Interoperability – RUN MAPS CACHE
 Run Map can be cached while running maps through WTXAP (WTX for
Application Programming) and WTXIS (WTX for Integration Servers)
 Edit dtx.ini and specify the maximum number of run map to be cached.
;use the following to define the max number of RUN maps to be cached in
the memory
;default value is 300, minimum value is 10
;set this value to -1 to disable RUN map caching
RunMapCacheMaxNum=300
36
© 2013 IBM Corporation
Industry Solutions
B2B and Commerce
Interoperability – DYNAMIC MAP CACHE (WMB/ IIB)
 The WMB/IIB Local
Environment
(LE.WTX.DynamicMapName)
is used with
LE.WTX.DynamicMap and
cacheMap switch.
 If cacheMap is set on a
DynamicMap, and there is a
DynamicMapName, caching
will be honored
 DynamicMapName is limited to
32 characters.
37
© 2013 IBM Corporation
Industry Solutions
B2B and Commerce
Interoperability – DYNAMIC MAP CACHE (WMB/ IIB)
 When using LE.WTX.Dynamic Map, the default map location will be:
– MQSI_WORKPATH/common/log/WTX/<ExeGrpName>/<FlowName>/
<WTXMapNodeName>/<MapName>
 If cacheMap switch is on a DynamicMap, and there is no
DynamicMapName , behavior is as prior - it will not cache the map.
eg : SET OutputLocalEnvironment.WTX.DynamicMapName = 'PreProcessEDI'
 Any RUN maps required by the LE.WTX.DynamicMap, will be relative to
the default map location.
38
© 2013 IBM Corporation
Industry Solutions
B2B and Commerce
Interoperability – DYNAMIC MAP CACHE (WMB/ IIB)
 Once a DynamicMap with a DynamicMapName is run with cacheMap, the
DynamicMap does not have to be retrieved from a repository on an
upstream node for subsequent invocations, although, the DynamicMap LE
must still be passed in (at least one "bogus" byte) along with the
DynamicMapName that was previously used.
SET OutputLocalEnvironment.WTX.DynamicMap = X'00';
39
© 2013 IBM Corporation
Industry Solutions
B2B and Commerce
Interoperability – Product Support
 WMB 8.0.0.3/IIB 9.0.0.1
 Sterling Integrator 5.2.4.2
 Business Processor Advanced 8.5
 IBM Integration Designer 8.5
 IBM DB2 10.5
 IBM Pure Systems V1.1 FP1/FP2 -- Pending Certification
 Smart Cloud Orchestrator v2.3 (SCO) – Pending Certification
40
© 2013 IBM Corporation
Industry Solutions
B2B and Commerce
Security – NIST COMPLIANCE

TLS V1.2 Protocol and NIST Compliance
 The advanced TLS V1.2 protocol and NIST compliance security mode are
now supported by the HTTP and FTP Adapters as well as the Launcher
Agent
 Introducing GSKIT security module that provides this higher level of
SSL/TLS security, but will only be activated once the accompanying IBM
GSKit product is installed and configured.
 If the IBM GSKit is not installed and configured on the library path of your
platform, the legacy TLS/SSL module, will continue to be used.
41
© 2013 IBM Corporation
Industry Solutions
B2B and Commerce
Security – NIST COMPLIANCE
 The IBM GSKit installation modules are provided in the "GSKit" subdirectory location of the WTX installation
 The IBM GSKit also provides X.509 certificate generation capabilities.
 An example is also available that will guide you along the installation and
setup steps that are required to ensure that existing and new maps can be
seamlessly run with greater levels of SSL/TLS-based security
42
© 2013 IBM Corporation
Industry Solutions
B2B and Commerce
Transformation & Standards Packs
New GA pack products…
IBM Standards Processing Engine Pack for Healthcare Payer
IBM Standards Processing Engine Pack for Supply Chain EDI
Updated pack products …
Healthcare
WTX Pack for HIPAA EDI 4.4.1.1 and 4.4.1.2
WTX Pack for HL7 4.4.1.1 and 4.4.1.2
WTX Pack for NCPDP 4.4.1.1 and 4.4.1.2
Supply Chain EDI
WTX Pack for EDI 2.8.1.1 (Pack for ASC X12, Pack for EDIFACT, Pack for
TRADACOMS)
WTX Trading Manager 8.2.1.7
WTX Pack SAP R3 8.3.2.1
Financial Services and Insurance
WTX Pack for SWIFT 4.3.2
WTX Pack for SEPA 4.3.2
WTX Pack for FIX 4.2.6
WTX Pack for ACORD Insurance 1.0.3.0
Sterling Integrator SWIFT/NACHA 5.2.4.2
43
© 2013 IBM Corporation
Industry Solutions
B2B and Commerce
IBM SPE Pack for Healthcare Payer
New Content…
All Functionality in the WTX Pack for HIPAA EDI 4.4.1.2 …PLUS
WEDI/SNIP Type 5 External Code Set Validation
• Choice of supplied Code Sets or Pattern Match enablement for
commonly applied validations
Partner/Message Type configuration
• WEDI/SNIP Levels 1-5 selections
• Claim Specific processing options
• Acknowledgement Reporting selections
Partner/Message Type specific processing enablement
• Deenvelope (Debulk) Processing
• Transformation Designation (using WTX, SI Mapper or XSLT)
• Envelope (Bulk) Processing
Partner/Message Type specific acknowledgments
• Control Number Schemes
• Syntax Overrides
44
© 2013 IBM Corporation
Industry Solutions
B2B and Commerce
IBM SPE Pack for Supply Chain EDI
New Content…
Partner/Message Type configuration
• Acknowledgement Reporting selections
Partner/Message Type specific processing enablement
• Deenvelope (Debulk) Processing
• Transformation Designation (Using WTX, SI Mapper or XSLT)
• Envelope (Bulk) Processing
Partner/Message Type specific acknowledgments
• Control Number Schemes
• Syntax Overrides
45
© 2013 IBM Corporation
Industry Solutions
B2B and Commerce
WTX Pack for ACORD Insurance 1.0.3
New Content…
ACORD DTCC Example
DTCC Data Structures for parsing and transformation
DTCC to/from ACORD XML TXLife format
Updated Content…
Updated ACORD PCS Version Support
Updated ACORD TXLife Version Support
Updated ACORD RLC Version Support
46
© 2013 IBM Corporation
Industry Solutions
B2B and Commerce
WTX Pack for HIPAA EDI 4.4.1.1
New Content…
Full Health Insurance Exchange (HIX) Payment 820 support – 005010X306
Example HIX 834 Enrollment support 005010X220A1
• Example parsing, and transformation using the CMS FFE
WTX Pack for HIPAA EDI 4.4.1.2
New Content…
Full ASC X12 PACDR Support
• Professional Claim Post Adjudication Reporting – 005010X298
• Institutional Claim Post Adjudication Reporting – 005010X299
• Dental Claim Post Adjudication Reporting – 005010X300
Example HIX 834 Enrollment support 005010X220A1
• Example parsing, and transformation using the CMS FFE
Updated Content…
Extension of Configurable Rules module
• Support Rule Driven WEDI/SNIP type 2 rules
• Continued support of WEDI/SNIP type 3 and 4 configuration
47
© 2013 IBM Corporation
Industry Solutions
B2B and Commerce
48
© 2013 IBM Corporation
Industry Solutions
B2B and Commerce
49
© 2013 IBM Corporation