1 Introduction

HSI-DataSync-OW, is a Spring Boot application that is responsible for providing one way synchronization of data from TESS to Salesforce.

Despite being a Spring Boot application, the build is configured to produce a .ear file: hsi-datasync-ow.ear

2 Configuration

Prerequisite:

Before configure setup for HSI-Datasync-OW, make sure already setup for HSI-Datasync-TCS, if not, please follow up HSI-Datasync-TCS (env related) setup.

Here only for HSI-Datasync-OW features and OW Data API related configuration (not include configuration with Salesforce).

2.1 WAS App Server System Properties

In WAS admin console, navigate to: Servers -> Server Types -> WebSphere Application Servers -> click the server of RGI -> on Configuration tab -> Java and Process Management -> Process definition -> Java Virtual Machine -> Custom properties. Define following properties.

Name	DEV	QA
hsi.owdata.authKey	B4665938-F2CD-49A5-A07E-4E8C387089FA	B4665938-F2CD-49A5-A07E-4E8C387089FA
hsi.owdata.base.url	https://mvtessinet01q.corp.toronto.ca	https://mvtessinet01q.corp.toronto.ca
hsi.owdata.userID	TCS001	TCS001

2.2 Proxy configuration for outbound API calls

In order to make outbound API calls to salesforce, we must define a proxy.

-Dhttp.proxyHost=proxy.toronto.ca

-Dhttp.proxyPort=8080

-Dhttps.proxyHost=proxy.toronto.ca

-Dhttps.proxyPort=8080

-Dhttps.nonProxyHosts={authentication host} | {OW DATA Api host}

nonProxyHosts	DEV	QA
authentication host	was-intra-qa.toronto.ca	was-intra-qa.toronto.ca
OW Data API host	mvtessinet01q.corp.toronto.ca	mvtessinet01q.corp.toronto.ca
-Dhttps.nonProxyHosts	was-intra-qa.toronto.ca\|mvtessinet01q.corp.toronto.ca	was-intra-qa.toronto.ca\|mvtessinet01q.corp.toronto.ca

Browser not supported