WTX 220.127.116.11 Release Contents Sunil Dandamudi – Architect, WebSphere Transformation Extendersdandamu@us.ibm.com
Agenda • Release • Details • Contents • Q& A
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
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
Productivity - PARSE • Usage Pattern • = PARSE (TEXT BLOB) • = PARSE (TEXT BLOB) + RULE Not Supported • = RULE + PARSE (TEXT BLOB) Not Supported
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))
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
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
Productivity - XVALIDATE Enhanced XVALIDATE function to support XML snippets The XML document no longer need a Prolog to be validated through XVALIDATE functions
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/xmlschema-1/#xsi_schemaLocation
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
Productivity – TEST DATA Select a group or item and use Generate Test Data context menu
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.
Adapter – SPE Adapter Command Line for SPE connectivity
Adapter – SPE Adapter Command Line options for SPE
Adapter – SPE Adapter Command Line options for SPE
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.
Adapter – SPE Adapter action commands are valid in maps that are running on WTX Launcher, Command Server, or the TX Programming Interface
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
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
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
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
Adapter – SPE Snapshot =PARSE(GET("SPE", "-DURL jdbc:derby://localhost:1527/spe2;user=derbyuser;password=derbyuser -DBDRIVER org.apache.derby.jdbc.ClientDriver -MAP parsewds -TRANSFORM -T", Input))
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 • Allows to configure multiple databases to test SPE on. This simplifies on-boarding multiple SPE environments (Test, Development and Production) with ease New Category
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
SPE – Design Studio (Preferences - Connectivity) • Allows to Define SPE Database Connectivity information • Multiple Database connections can be setup for each user environment
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
SPE – Design Studio • Allows to Check-in • XSLT • Sterling • WTX • Allow to Test maps inline on SPE engine • XSLT • Sterling • WTX
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
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.
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.
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';
Interoperability – Product Support • WMB 18.104.22.168/IIB 22.214.171.124 • Sterling Integrator 126.96.36.199 • 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
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.
Security – NIST COMPLIANCE • The IBM GSKit installation modules are provided in the "GSKit" sub-directory 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
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 188.8.131.52 and 184.108.40.206 • WTX Pack for HL7 220.127.116.11 and 18.104.22.168 • WTX Pack for NCPDP 22.214.171.124 and 126.96.36.199 • Supply Chain EDI • WTX Pack for EDI 188.8.131.52 (Pack for ASC X12, Pack for EDIFACT, Pack for TRADACOMS) • WTX Trading Manager 184.108.40.206 • WTX Pack SAP R3 220.127.116.11 • 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 18.104.22.168 • Sterling Integrator SWIFT/NACHA 22.214.171.124
IBM SPE Pack for Healthcare Payer • New Content… All Functionality in the WTX Pack for HIPAA EDI 126.96.36.199 …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
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
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
WTX Pack for HIPAA EDI 188.8.131.52 • 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 184.108.40.206 • 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