In this section: |
This section provides release notes that are applicable for specific iWay Adapters in iSM Version 6.1.9.
This section provides release notes for the iWay Application Adapter for mySAP in iSM Version 6.1.9.
Exceptions not reported to host system issue is resolved. If the SAP system goes down or an exception is thrown, the results are not reported back to SAP and IDoc data is lost. This is corrected by a combination of the mySAP3 adapter in this release and iWay Service Manager changes. If a process flow should fail, the result should now be reflected back to SAP and in SM58 (transaction monitor) the message "Process Flow Failed" should be displayed.
File Emitter ignores errors issue is resolved. When using the adapter in a channel or process flow, the adapter did not respond to failure exceptions. The resolution is not to use a "file emitter" in a flow or channel which does not emit a status. The proper implementation is to use a "file emit agent" (available from the "Services" in the iWay Registry). The file emit agent will report a success or failure, on failure or exception, the mySAP3 adapter will now throw an exception back to SAP and the transaction will not be "lost".
Data or Time fields throw exception on empty records issue has been resolved. When a Date or Time field is incorrectly filled or has a null value, the exception "JCO_ERROR_CONVERSION: Unparseable date: "00" in record" was thrown. The new correct behavior is to ignore a date that is null or empty (causing zeroes). The SAP rules for these fields can be found in the SAP help files under "System fields for Date and Time".
This section provides release notes for the iWay Application Adapter for Microsoft Dynamics CRM in iSM Version 6.1.9.
There is a known issue in MSCRM 2007 adapter where an invalid port destination in a SOAP message throws the exception "Error in Process DB XDFail" instead of "error getting target MSCRM2007". This issue is currently being investigated.
Credentials file cannot be located when running as a service known issues:
Incorrect Command Syntax Resolved Issue
When starting the iWayRoutingService.exe application, the correct command to store credentials is now:
iWayRoutingService.exe -setcredentials {username} {domain} {password}
Some previous releases of the adapter contained sample program source code files that should not have been published. This is corrected in 6.1.9 and sources are removed.
Version 3 of the iWay .NET Technology Adapter is introduced with this release. It is not completely schema or XML compatible with previous versions. This version introduces support for constructors, sessions, database connections and greatly enhanced metadata capabilities.
The adapter is designed to work with method calls contained in .NET assemblies, the source code input is not used only the Common Intermediate Language (CIL).
The adapter has been tested with .NET framework runtime 3.5, 4.0 and 4.5 on Windows client and server machines. No other platforms are currently supported.
While the new enhancements open new areas of the .NET framework to use with the adapter, some parts of the framework remain out of scope and are explicitly not supported:
No explicit or implicit guarantee of compatibility or performance with user application components is given with the iWay .NET Technology Adapter, due to the scope of the framework being too wide. If you have questions about supported components of .NET or application compatibility, contact your local IBI support office.
Some of the resolved issues include:
For a complete list of adapter enhancements, see the iWay .NET Technology Adapter User's Guide.
As of iSM Version 6.1.9, Web Mode applications as described in Chapter 4, Using Web Mode in the iWay Emulation Adapter (3270/5250) User's Guide is deprecated. It will be de-supported with next release of iWay Service Manager. Web Mode customers may consider migrating to a user written servlet that calls the Java API directly.
As of iSM Version 6.1.9, the iWay Technology Adapter for RDBMS supports the XMLType data type for Oracle databases. If you are planning to use this functionality, then the adapter requires the xdb6.jar and xmlparserv2.jar files to be installed with the ojdbcx.jar driver. These JAR files are not included with the iSM distribution and must be obtained from Oracle. Versions of these JAR files should match and correspond with the version of the Oracle database engine being used.
iWay Application Adapter for MUMPS only supports InterSystems Caché databases on Windows platforms.
This section provides release notes that are applicable for specific iWay E-Business Adapters in iSM Version 6.1.9. For more information, see the iWay Integration Solution for EDI User's Guide, iWay Integration Solution for SWIFT User's Guide, and iWay Integration Solution for HIPAA User's Guide.
This is the final release of SWIFT 2013. All components, documentation and sample channels have been updated. Updated Ebix files are available for download from http://techsupport.ibi.com. Note that many documents did not have an update in SWIFT 2013 and remain as they were in SWIFT 2012.
Due to component requirements, SWIFT will no longer be supported on any releases prior to 6.1.8.
New versions of SWIFT will only be supported in the current release of iWay Service Manager.
Due to component requirements, the following components are deprecated and are not included in this release:
All metadata Ebix can be downloaded from http://techsupport.ibi.com. Full instructions are available in the user guides. The metadata naming convention is now consistent with other Ebix, and may require changes. The iWay Integration Solution for SWIFT User's Guide describes the differences in the template name patterns. The sample channels attached to the manual now included.
The use of Dictionary Builder to modify SWIFT metadata is not supported in this release.
This section provides release notes that are applicable for iWay Integration Solution for HIPAA in iSM Version 6.1.9.
This section provides release notes that are applicable for iWay Integration Solution for EDI X12 in iSM Version 6.1.9.
This section provides release notes that are applicable for iWay Integration Solution for EDIFACT in iSM Version 6.1.9.
This release introduces the new MLLP listener and emitter for HL7. The current MLLP listener is a combination component that includes a listener, preparser, and emitter. A series of components are now offered where each offer separate functionality. This will allow the user to create HL7 channels that are in the traditional iSM model (Inlet - Route - Outlet) and will allow use of a process flow for further processing and / or routing. The New components are functionally the same. You can now route messages within a process flow to success or fail paths and perform after-transformation processing on the failed messages, such as outputting to a separate queue or sending an email notification. All HL7 metadata is included this release.
Supported and Documented
Made Invisible and May Be Deprecated
Removed
Config\Base\HL7
Type Code |
Rule Method |
---|---|
DT |
isDate |
NM |
isNumeric |
SI |
isSequenceID |
ST |
isString |
TN |
isTelNo |
TM |
isTime |
TS |
isTimeStamp |
This functionality can be controlled optionally with a switch in the preparser and preemitter. Data type validation is not designed to replace schema validation (see below) but may offer some flexibility to the user for validation. Note that mandatory segments and elements are enforced by the Req attribute in the dictionary and are not affected by this setting.
com.ibi.edaqm.XDEDIError.setData_element_syntax_code(I)V - No such method error.
If you receive this error, rename or remove the iwhl7.jar file from the \lib directory.
If you decide to use the second workaround, it is recommended that you open a support case with customer support unless you are extremely familiar with ebix structures.
This section lists ANSI X12, VICS, UCS, and HIPAA documents that are supported in the latest release.
Version |
Document |
Version |
Document |
---|---|---|---|
2001 |
All |
4010UCS |
All |
2002 |
All |
4010VICS |
All |
2003 |
All |
4020 |
All |
2040 |
All |
4030 |
All |
3010 |
All |
4030UCS |
All |
3010VICS |
All |
4030VICS |
All |
3020 |
All |
4040 |
All |
3020VICS |
All |
4050 |
All |
3021 |
None |
4060 |
All |
3030 |
All |
5010 |
All |
3040 |
All |
5010UCS |
All |
3040VICS |
All |
5010VICS |
All |
3040UCS |
All |
5020 |
All |
3050 |
All |
5030 |
All |
3050VICS |
All |
5040 |
All |
3060 |
All |
5050 |
All |
3070 |
All |
6010 |
All |
4010 |
All |
6020 |
All |
6030 |
All | ||
HIPAA: | |||
4010A1 |
All |
5010X217 |
278 |
5010 |
997, 999 |
5010X218 |
820 |
5010X186 |
824 |
5010X220A1 |
834 |
5010X187 |
269 |
5010X221A1 |
835 |
5010X210 |
275 |
5010X222A1 |
837P |
5010X211 |
275 |
5010X223A2 |
837I |
5010X212 |
276, 277 |
5010X224A2 |
837D |
5010X213 |
277 |
5010X225A2 |
837R |
5010X214 |
277u |
5010X231A1 |
999 |
5010X215 |
278 |
5010X279A1 |
270, 271 |
5010X216 |
278 |
5010X306 |
820 |
5010X307 |
834 |
Note: Any documents that are not included in this release are available upon request.
This section lists EDIFACT documents that are supported in the latest release.
Version |
Document |
Version |
Document |
---|---|---|---|
D93A |
All |
D01C |
All |
D94A |
All |
D02A |
All |
D94B |
All |
D02B |
All |
D95A |
All |
D03A |
All |
D95B |
All |
D03B |
All |
D96A |
All |
D04A |
All |
D96B |
All |
D04B |
All |
D97A |
All |
D05A |
All |
D97B |
All |
D05B |
All |
D98A |
All |
D06A |
All |
D98B |
All |
D06B |
All |
D99A |
All |
D07A |
All |
D99B |
All |
D07B |
All |
D00A |
All |
D08A |
All |
D00B |
All |
D08B |
All |
D01A |
All |
D09A |
All |
D01B |
All |
D09B |
All |
D10A |
All | ||
D10B |
All | ||
D11A |
All | ||
D11B |
All | ||
D12A |
All | ||
D12B |
All | ||
UNCONTRL |
CONTRL |
This section lists SWIFT documents that are supported in the latest release.
Version |
Document |
---|---|
2010 |
All |
2011 |
All |
2012 |
All |
2013 |
All |
Note: For updated Ebix information, refer to http://techsupport.ibi.com.
This section lists HL7 documents that are supported in the latest release.
Version |
---|
2.1 |
2.2 |
2.3 |
2.3.1 |
2.4 |
2.5 |
2.6 |
This section lists the supported separators and delimiters for the preparsers and preemitters.
Hex |
Char |
Hex |
Char |
Hex |
Char |
---|---|---|---|---|---|
01 |
SOH |
16 |
SYN |
2F |
/ |
02 |
STX |
17 |
ETB |
3A |
: |
03 |
ETX |
18 |
CAN |
3B |
; |
04 |
EOT |
19 |
EM |
3C |
< |
05 |
ENQ |
1A |
SUB |
3D |
= |
06 |
ACK |
1B |
ESC |
3E |
> |
07 |
BEL |
1C |
FS |
3F |
? |
08 |
BS |
1D |
GS |
40 |
@ |
09 |
TAB |
1E |
RS |
5B |
[ |
0A |
LF |
1F |
US |
5C |
\ |
0B |
VT |
21 |
! |
5D |
] |
0C |
FF |
23 |
# |
5E |
^ |
0D |
CR |
24 |
$ |
5F |
_ |
0E |
SO |
25 |
% |
60 |
' |
OF |
SI |
26 |
& |
7B |
{ |
10 |
DLE |
27 |
' |
7C |
| |
11 |
DC1 |
28 |
( |
7D |
} |
12 |
DC2 |
29 |
) |
7E |
~ |
13 |
DC3 |
2A |
* |
7F |
DEL |
14 |
DC4 |
2B |
+ | ||
15 |
NAK |
2D |
- |
iWay Software |