Before installing, configuring, and using the adapter, you must understand its environmental requirements:
The adapter framework that an adapter uses must be compatible with the version of the integration broker (or brokers) with which the adapter is communicating. The 1.0 version of the adapter for ACORD XML is supported on the following adapter framework and integration brokers:
See the Release Notes for any exceptions.
Note: For instructions on installing the integration broker and its prerequisites, see the following documentation.
For WebSphere InterChange Server (ICS), see the System Installation Guide for UNIX or for Windows.
For message brokers (WebSphere MQ Integrator Broker, WebSphere MQ Integrator, and WebSphere Business Integration Message Broker), see Implementing Adapters with WebSphere Message Brokers, and the installation documentation for the message broker. Some of this can be found at the following Web site: http://www.ibm.com/software/integration/mqfamily/library/manualsa/. For WebSphere Application Server, see Implementing Adapters with WebSphere Application Server and the documentation at: http://www.ibm.com/software/webservers/appserv/library.html
The adapter is written to the the following versions of the ACORD standards.
The adapter is supported on the following platforms:
The adapter has the following software prerequisites and other dependencies:
The XML Object Discovery Agent (ODA) must generate business objects representing all of the possible message types in the ACORD XML Property & Casualty schemas. However, the size of the resulting data exceeds the capacity of the application-specific information (ASI) where this data is stored. To avoid these limits at run-time, edit the Property and Casualty Schemas/DTDs to reduce the number of message types in the entities.
For example, the "Insurance Service Request" schema has many choice elements representing various message types. You can remove any message types you don't anticipate using in order to accomodate the remaining types within the confines of the ASI size limitations.
For more information, please refer to the Business Object Development Guide.
The connector has been internationalized so that it can support double-byte character sets, and deliver message text in the specified language. When the connector transfers data from a location that uses one character code to a location that uses a different code set, it performs character conversion to preserves the meaning of the data.
The Java runtime environment within the Java Virtual Machine (JVM) represents data in the Unicode character code set. Unicode contains encoding for characters in most known character code sets (both single-byte and multibyte). Most components in the WebSphere business integration system are written in Java. Therefore, when data is transferred between most integration components, there is no need for character conversion.
To log error and informational messages in the appropriate language and for the appropriate country or territory, configure the Locale standard configuration property for your environment. For more information on configuration properties, see Appendix A, Standard configuration properties for connectors. Footnotes: