iWay Service Manager 6.01 Product Update
Chris Bevilacqua
iWay Solutions Architect
Copyright 2010, Information Builders. Slide 1
Agenda
 iWay 6.0.1 overview
 Detailed feature dive
 IWay Integration Tools
iWay 6.0.1: Generally Available
 Available
September 30, 2009
 Downloadable from techsupport.ibi.com
 All software, metadata, features and maintenance follow
corporate download philosophy
iWay 6.0.1: Generally Available
 Includes
 Application Adapters
 MySAP
 RDBMS adapter
 eBusiness Adapters
 EDI X12
 SWIFT
 Trading Partner Manager
iWay 6.0.1: Additional Adapters
 Additional Adapters delivered as Multiplatform
enhancements
 Application Adapters
 J. D. Edwards One World
 J. D. Edwards Enterprise One
 People Soft
 Siebel
 eBusiness Adapters
 Business Activity Monitor
iWay 6.01: Maintenance Strategy
 Console Plug-in to display applied maintenance
 Third party jars
 First cut: save results to file
 Future: Post results directly to case (Hottrack)
iWay 6.0.1: Maintenance Strategy
iWay 6.01: Maintenance Strategy
 Multiplatform Enhancements
 Vehicle to deliver new features/adapters
 Includes one adapter feature per deliverable such as
PeopleSoft or Siebel Adapters
 Multiplatform Patches
 Monthly cumulative patches
 Support patch rollback (remove)
 Smart Install
 Only install components that are already in your
environment.
iWay 6.0.1 Cumulative Patch 6: Generally Available
 Includes
 Technology Adapters
 Log Event Adapters
 Informix
 Oracle
 SQL Server
 Application Adapters
 Previous
 JDE,JDEW,MySAP,Peoplesoft,Siebel
 New
 Salesforce.com
iWay 6.0.1: Cumulative Patch 6
 Includes
 eBusiness
 Business Activity Monitor
 EDI/X12
 Metadata is downloaded separately
 Both Pipeline and Non Pipeline metadata available
 EDIFACT
 Select EDI/X12
 Download EDIFACT metadata
 EDIFACT only has pipelined metadata.
iWay 6.0.1: Cumulative Patch 6
 Includes
 Extensions
 Recommend : telnet extension always be selected
 DQC
 601
 Coreq: iIT/DQC bundle downloadable from
techsupport
 Real Time Data replication.
 Coreq iIT – Data Integration objet
iWay 6.0.X Roadmap
iWay 601 Feature Dive
Copyright 2010, Information Builders. Slide 13
iWay 6.0.1: General Settings
 Focus of 6.0.x is standards
 Complete XPATH1
 xpath1(sstmt [,map] [,object]):
 xpath(‘//x’,,sreg(‘oldtree’))
 Full specification (via Xalan)
 http://www.w3.org/TR/1999/REC-xpath-19991116
 Old XPATH now _iwxpath
 http://www.w3.org/TR/1999/REC-xpath-19991116,
section 2.5, Abbreviated Syntax
iWay 6.0.1: General Settings
 To maintain backward compatability default XPATH is
iWXPATH
 Can choose to use XPATH 1.0
iWay 6.0.1: General Settings
 Transform Caching
 Performance impact
 Settings may vary
 Development
 Production
iWay 6.0.1: Providers
 Centralize resource controls
 Available to many component
 Reached through JNDI
 Used in 6.0.x Components
 nHTTP, nAS/2
 SQLAgent, RDBMS Adapter, LDAP
 XALog, FTPServer
iWay 6.0.1: Providers
 Security Provider:
 Keystore
 SSL
 Certificate Stores
 Data Provider (JDBC pools)
 Directory Provider (LDAP)
 Namespace Map (for XPATH)
 Pooling (HTTP Client Connections)
 Authentication realm
 Data Quality
iWay 6.0.1: Providers
 Pools connections/statements system wide
 JNDI DataSource
 Server is the default context
 Rich options for pool management
 Size and timeout management
 Can validate connection on borrow/return
 Action on exhaustion
 Fail, block or grow
 Pflow can be a borrower -- transactionality
iWay 6.0.1: Providers
 Provider defined to a manage server
iWay 6.0.1: Providers
 Use with Adapters for example RDBMS Adapter
iWay 6.0.1: Providers
 Show Pools command
Pools:
JDBC Connection Providers
mssql
URL: jdbc:sqlserver://iwayntk4:1433;databaseName=CenturySales
idle: 4, busy: 1, borrowed: 2, rtd: 1
 Show Providers command
Enter command:>providers
consolerealm
com.ibi.providers.XDConsolerealmProvider@cc5002
jdbc
URL: jdbc:sqlserver://iwayntk4:1433;databaseName=CenturySales
idle: 0, busy: 5, borrowed: 794, rtd: 789
iWay 6.0.1: Providers
 Services to be used in conjunction with Providers.
 Providers are in the server/not registry
 Can only test run against configuration
 Move providers from one system to another via packages
 Current components that use providers
 DQC
 RDTR
 Services: for example SQL Agent
iWay 6.0.1: Services
 Services to be used in conjuncction with Providers.
 SQL object (com.ibi.agents.XDSQLAgent)
 Use JNDI true
 JNDI Name
 JNDI Factory
 Important: do not use Pool Connections parameter
 Pooling of connections handled by provider
iWay 6.0.1: Services

iWay 6.0.1: Services
 Test run
 Against registry: ???
<eda>
<error timestamp="2010-04-19T00:30:31Z" code="6" stage="AGENT" source="SQL">XD[FAIL] cause: 0 subcause: 0
message: SQLAgent cannot find the datasource jdbc/NTK4SQL in local JNDI service.</error>
</eda>
 Against configuration:
<iway>
<response totalrows="1">
<cncresult>
<result format="std">
<resultset rowcount="1">
<colinfo>
<col length="11" offset="0" type="4" nullable="1">NO_COLUMN_NAME</col>
</colinfo>
<row>9
</row>
</resultset>
</result>
</cncresult>
<timestamp>2010-04-19T00:34:13Z</timestamp>
<execstatus>0</execstatus>
</response>
</iway>
iWay 6.0.1: Services
 Error handling
 Handle each error/retry situation individually
iWay 6.0.1: Services
 Error Handling process flows can be accomplished a number
of different ways. Some of the possible methods are
 Explicitly checking for an error post agent execution by


conditioning the edge with onError or onFailure or with a
specific error code or status based on the agent.
A outlet conditioned with _iserror()
An XDCatchAgent can be put into the beginning of the
channel. This channel has two edges on the output side
that is used for processing. The first is the onCompletion
edge. The second is the onCustom with the onError and
onFailure cases selected.
iWay 6.0.1: Services
 XDCatchAgent
 concept of the XDCatchAgent is similar to that of a try
catch block in java
two edges off of this agent:
 onCompletion (blue)
 “happy-path” thread of execution. The thread of
execution passes down this edge during normal
operation. The XDCatchAgent has no effect on the
flow when the thread of execuition is going “forward”
through the agent. Once past the XDCatchAgent
the flow of execution operates in the normal manner
 onCustom (brown).
iWay 6.0.1: Services
 XDCatchAgent
 two edges off of this agent:
 onCompletion (blue)
 onCustom (brown).
 If an unhandled failure or error is detected in the
flow, the thread of execution backs up to the
nearest XDCatchAgent. The thread of execution
then flows down the OnError or ofFailure edges
coming from the XDCatchAgent that were
configured on the onCustom edge wizard.
 A common use of a catch would be to run a
compensating transaction or to generate an error
receipt or notification
iWay 6.0.1: Services
 XDCatchAgent
 Multiple XDCatchAgent (s) can be put into a process flow.
 The error branch is taken off of the closest XDCatchAgent
previous to where the error occurred. In this manner,
multiple error conditions can be coded for a given flow if
needed.
iWay 6.0.1: Services
 XDCommitAgent
 When operating in Local Transaction mode
 commit or roll back operation to take place immediately
 Once committed, the data cannot be rolled back
regardless of the manner in which the flow actually ends.
 A common use: catch node.
If catch traps an error, the
error edge might issue a roll back and then proceed to
take other action to record or recover from the error.
iWay 6.0.1: Services: XDSREGAGENT
 Type of SREGS
 USR
 HDR – SREG values placed in protocol hdrs e.g. MQ
RFH2 etc.
iWay 6.0.1: Services: XDSREGAgent
 Add, Delete
 Scope of SREGS
 Thread only found on the line of the flow (think multiple
branches
 Flow anywhere in the flow, also sreg values are
passed to the subflows.
 Message SREG is on worker level – including emitters.
Sreg value is reset when worker is recycled.
 Channel on master level. Lives on after worker
recycled. Useful for maintaining counters on a channel
 Server across channels
iWay 6.0.1: iWay Functional Language
 functions to obtain values for configuration use.
 iWay Service Manager uses conditional expressions to
select routes in a channel. A conditional expression is a
string composed of any combination of the evaluation
functions listed here that returns a boolean result.
 Literals are explicit numbers or text used in an expression
 Testing functions
 tool testfuncs
 Tool tesfuncs C:\iway\a123.xml
iWay 6.0.1: iWay Functional Language
 Help funcs
Enter command:>help funcs
_add
_after
_all
_any
_attcnt
_atthdr
_atthdric
_base64
_ceil
s
_count
_chaninfo
_concat
_cond
_contain
_datediff
_dateof
_ddiv
_decode64
_dadd
_deentity
_div
_before
_dmul
_cat
_dsub
 Help func xxx
Enter command:>help func jdbc
_jdbc Return one column value from an SQL operation.
1 provider required Name of a preconfigured JDBC provider.
2 statement required An SQL select or call statement.
3 timeout optional Number of seconds to wait for response. Default
is 2 seconds.
4 default optional Default to return if the named column has no val
ue.
iWay 6.0.1: iWay Functional Language
 New IFL
 Log command _log()
write message to iWay log
 Regex _regex() vs _replace
 regular expression vs character
 Set SREG _setreg()
iWay 6.0.1: iWay Functional Language Editor
 iWay Integration Tools
 File  New  iWay Integration  expression
iWay Service Manager 6.0.1: Operation and
Management Enhancements
 iWay Telnet extension
 Used to remotely access the iSM 6.0.1
 A Telnet client session can connect to any iSM instance

running either in the foreground or the background.
Helpful when access to the command line console
cannot be performed locally when the iSM instance is
running in the background, for example, a Windows
service.
iWay Service Manager 6.0.1: Operation and
Management : Telnet extension
 iWay Telnet extension
 One telnet listener required per Server
 Not per configuration
 show configs
Enter command:>show configs
* base
Server Uptime: 7 minutes
telnet port=23
raw
Server is down
training Server Uptime: 9 hours, 29 minut
 remote training
Enter command:>remote training
remote to 'training' set
iWay Service Manager 6.0.1: Operation and
Management : Telnet extension
 iWay Telnet extension
 Scripting for lights out operation
 set cmdstatus = on
#!/bin/sh
host=localhost
port=9023
cmd="info"
( echo open ${host} ${port}
sleep 1
echo "iway"
sleep 1
echo "iway"
sleep 1
echo ${cmd}
sleep 1
echo quit ) | telnet > /home/jay/out.txt
echo " "
echo "* * * command output start * * *"
cat /home/jay/out.txt
echo "* * * command output end * * * *"
echo " "
iWay Service Manager 6.0.1: Operation and
Management : Telnet extension
 iWay Telnet extension command return codes
































SCMD
1000
2000
3000
5000
6000
9999
6001
1002
3009
5010
5011
3012
2002
6101
5101
5007
3022
3023
2021
5021
3023
2023
2004
5121
2005
1031
2014
2005
2006
2007
2700
0
Command successful
General security not otherwise explained
General syntax error
Resource error - the component or item called upon returned an error
Specification error: Although the syntax was right the combination of information was not
IO: Some I/O error occurred
Error not categorized
Cannot remote the specified command. For example, cannot issue a 'remote' command in remote mode
Principal in effect did not allow the command to run
Cannot parse the external configuratikon file in a PULL command
Unknown configuration for PULLcommand
Provider class is not recognizedin the PULL command
Provider class not found in PULL cmmand
Name of an external tool is not specified in TOOL command
Unable to read dictionary in PULL command
Tool not found to execute
Tool specified is not a valid iWay server tool
Tool failed with reported exception
Tool failed with reported runtime exception
No remote setting offered
Remote configuration is not configured on this installation of the server
Remote configuration <name> is not running. The configuration must be running to execute commands.
Unable to remote to own configuration.
The name of a master/channel is required and was not entered
Names master/channel was not valid
Master/channel name is required for comand and it is missing.
Register name is restricted. You cannot set a configuration or other restricted special register's value
Invalid value expression: needs a document. You cannot use iFL expresisons to set a register vlaue if the
RUN command requires a path to a command file
<line number> in run script has a syntax error
<line number> in run script has a, iFL syntax error
Syntax, a member of a list of values is not valid
iWay Service Manager 6.0.1: Operation and
Management : Telnet extension
 Useful command
 Showlog view traces from telnet session
 Hidelog turn off log
 Spool filename
 set active [on|off] -m channelname
 Set debug on – m channelname -save
iWay Service Manager 6.0.1: Adapter Updates
 .NET Adapter
 Be able to call .NET assemblies via the adapter
without having to recompile the original assembly.
 Be able to consume legacy COM servers via the
adapter.
 Support for passing complex parameters and return
types
 Be able to create schema for complex data types.
When not available return xsd;any.
 Available with Cumulative Patch 6.
iWay Integration Tools: Development Tools
 New iWay Integration
Tools
 Combines:
 Explorer
 Transformer
 Designer
 Configuration
 Extensible via Eclipse
 Based on Eclipse 3.4
 CFR: November
iWay Integration Tools
 Release
 CFR released on the 11/09.
 CFR first update release on 12/02.
 Going production soon
 Available via techsupport.ibi.com.
 Update site http://updates.ibi.com/iit
 Will provide updates for the CFR into production.
 DQC integrated builds are also available
iWay Integration Tools
 Features
 IFL editor available.
 Data Integration Extension support through the Data
Integration Object.
 iWay Integration Tools Getting Started Guide available
now.
iWay Integration Tools
 Roadmap
 Short term:
 Object and property search in designer
 Test Result Editor in designer
 Variable support in transformer
 Long Term:
 Channel Editor.
iWay Integration Tools
 Customer Feedback:
 We love and need feedback!!!
 Hottrack cases for bugs.
 New Feature Requests/Usability enhancements
 Hottrack.
 Email to feedback@iwaysoftware.com.
iWay Documentation enhancements
 Documentation Services customer feedback program
 Build a strong, focused connection between customers
and the product development team
 Goal is to develop a pool of users across
 Quick Start manuals for key products
the product line
iWay Documentation enhancements
 Infocenter :
 Eclipse plug-in for iWay 6.0.X documentation
 Searchable across the full document library
 http://ecl.informationbuilders.com/iway/index.jsp
iWay Documentation enhancements