ACORD Data Exchange Platform & Translator
Introduction #
This document describes how to set up ACORD message integration between the Adept gateway and SICS as a scheduled job. All the required functionality is included in SICS System Administration Utility, but custom configuration is required.
Prerequisites #
- The URL’s, Subscription and credentials of ADEPT , OAuth Broker details (send as Cedent) and/or OAuth Reinsurer (receive Assumed) should be obtained from ADEPT Services.
- The SICS eMessaging WebService Interface must be running. For installation instructions please see: SICS eMessaging Server.
Configure access to servers #
The messaging integration is configured in file conf\sics.emessaging.integration.properties. The various entries are documented within the file itself. The file follows Java property file syntax. Lines that begin with a ‘#’ are comments and will be ignored.
The most important properties are the URLs to the server systems.
#Message Source System
source.system.implementation=com.dxc.adept.client.AdeptClient
#Target System
target.system.implementation=com.csc.sics.acord.util.SicsAcordClient
#URL of SicsEMessagingServer (a.k.a. acord.soap)
acord.soap.server.url=http://localhost:12942/acord.soap/wsdl/MyAcordMsgService.wsdl
#URL's of ADEPT
adept.url=https://uat-adept.acordsolutions.net
adept.ds.url=https://uat-adept.acordsolutions.net/grlc/v1/
adept.grlc.url=https://uat-adept.acordsolutions.net/grlc/v201610/
adept.ds.url.techaccounts.search=https://uat-adept.acordsolutions.net/grlc/v1/techAccounts/_search
adept.ds.url.claims.search=https://uat-adept.acordsolutions.net/grlc/v1/claims/_search
adept.ds.url.settlements.search=https://uat-adept.acordsolutions.net/grlc/v1/settlements/_search
adept.grlc.url.techAccount=https://uat-adept.acordsolutions.net/grlc/v201610/techAccounts/
adept.grlc.url.claim=https://uat-adept.acordsolutions.net/grlc/v201610/claims/
adept.grlc.url.settlement=https://uat-adept.acordsolutions.net/grlc/v201610/settlements/
#OAuth Broker details (Cede):
adept.client.id.broker=CLIENT_ID
adept.client.secret.broker=CLIENT_SECRET
adept.access.token.url=ACCESS_TOKEN_URL
#OAuth Reinsurer details (Assumed):
adept.client.id.reinsurer=CLIENT_ID
adept.client.secret.reinsurer=CLIENT_SECRET
#Query Url's
adept.techAccount.query.url=https://uat-adept.acordsolutions.net/techAccounts/
adept.claims.query.url=https://uat-adept.acordsolutions.net/claims/
#Include messages from created date
adept.filter.include.messages.created.from.days.ago=
The no.of days must be given for the adept.filter.include.messages.created.from.days.ago= in properties file. When ADEPT plug-in is in running the messages created n(based on inpout value) days ago are considered for transferring into SICS.
Define scheduled job #
In order to carry out message integration, a scheduled job must be set up. General information on defining and scheduled jobs can be found in the SICS System Admin Guide. For scheduling Adept integration, the job step type “Generic Java Process” must be added with the parameter com.csc.sics.emessaging.gateway.integration.SicsEMessagingGatewayRouter

Configure logging #
Log output of the message integration scheduled job, is configured as part of the standard SICS log configuration in conf/log4j2.xml in the scheduler (stand-alone or SICS Batch Server). The relevant logger name is com.csc.sics.emessaging.integration.Routing.
Since the scheduled job runs unattended, one may set up additional notification (e.g. email, windows event log etc.) in case of FATAL and ERROR messages. For details on how to set up such an appender, please refer to log4j2 documentation on how to set up appropriate appenders: https://logging.apache.org/log4j/2.x/
In addition progress and error messages will be written to the job step log. In case the log statements are not displayed in chronological order, right click on the left column heading to sort all statements:

eMessages Import #
Step-by-Step process to transfer the messages from ADEPT to SICS
-
eMessaging Server: Ensure that the emessaging server is up.
-
Configure Access: Ensure that the configuration is correctly set up in “conf\sics.emessaging.integration.properties”.
-
Scheduler setup: Ensure that the scheduler is correctly setup.
-
Run Scheduler: Running the scheduler for the ADEPT Integration Plug-in transfers the messages (CMs,TAs and Settlements) from the ADEPT to eMessaging server. Messages in “awaiting response” status are moved.
-
Import messages: The eMessaging server imports these messages into SICS. Before importing, the server records the UUIDs of the received messages.
-
Query: Once the messages are generated with acknowledgements, and these acknowledgements are either accepted or rejected, an API will be called. This API will update status of the messages in ADEPT to either Queried, Accepted or Rejected based on the type of acknowledgements generated in SICS. The API checks acknowledgements for messages with the external system identifier code “ADEPT”.

-
External System Identifier: External system helps to differentiate the messages based on the import process, with two possible values:
- ADEPT. The default eMessaging External system code for ADEPT or the input value given to the target.system.code in the conf\sics.emessaging.integration.properties file.
- GATEWAY.
The Reference data table code for eMessaging External system is “01239”.
-
Handling of unacknowledged Messages: The messages that have not yet generated acknowledgements in SICS remain in the status “Awaiting Response” in ADEPT. Running the ADEPT Plug-in again will attempt to transfer these messages from ADEPT to the SICS. But, the eMessaging server checks for duplicate messages based on the message UUIDs and only imports the messages that are not yet imported into SICS.
Configure JAX-WS Provider #
If you are running the scheduler job from the command-line see:
SICS Installation Guide - Appendix C - Command Line Parameters, you must change the default JAX-WS Provider to org.apache.axis2.jaxws.spi.Provider in runtime/conf/META-INF/services/javax.xml.ws.spi.Provider