To integrate Assure or ER with DQ+, we need to create an Application id in DQ+. Once the ID has been created we need to modify IA.properties under {Infogix_Assure_install_Home}/config/{Config.name}/IA/.
Note: The instructions below same steps to Integrate ER with DQ+. For ER you have to modify ER.properties instead of IA.properties. You may use same Application ID for both IA & ER.
Initial Setup
- Within Data360 DQ+, Create an Application User.
Modify IA.properties or ER.properties
You will need to modify IA.properties for Assure installations and/or ER.properties for ER installations. The same instructions below apply to both property files.
- IA.properties file are found in the following directory:
{Infogix_IA_install_home}\config\{IA_config_name}\IA\IA.properties
and ER.properties are found in the following directory:
{Infogix_ER_install_home}\config\{ER_config_name}\ER\ER.properties
- Open the property file in a text editor and modify following properties with your DQ+ installation information:
################################################################################
# properties for Data3Sixty Analysis/Validate/Case Management (Cafe) integration
################################################################################
# comma separated list of email addresses to notify of a Sagacity push failure.
SAGACITY_PUSH_FAILURE_EMAILS=
CAFE_GATEWAY_ENABLED=true
# Cafe deployment mode [cloud]
CAFE_DEPLOYMENT_MODE=enterprise
# The url to cafe.
CAFE_URL=http://sampleurl.infogix.com
# The user name to use when communicating with cafe.
CAFE_USER_NAME=sampleemailaddress@infogix.com
# The password to use when communicating with cafe.
CAFE_USER_PASSWORD={password_removed}
# The cafe environment. This must be the name of an environment defined in Cafe.
# Solution deployments that may use the same entities across multiple deployments
# must use different environments if they are pointing to the same instance
# of Cafe. For example, if there are three instances of Assure pointing to the
# same Cafe instance and if both could have the same control entities in them
# (by export/import), then each of these assure instances must push to a different
# environment in that Cafe instance, such as Dev, Test, and Prod.
CAFE_ENVIRONMENT=Pilot1_Assure_ENV
# A unique id that identifies this solution instance. The same id must be used across
# all environments dev, test, production etc. For example, if you deploy separate
# Assure systems for different lines of business, and they will both use the same
# Cafe/Sagacity system, use different unique IDs for each Assure line of business
# installation.
CAFE_SOLUTION_UNIQUE_ID=${solution.short.name}
# Flag to indicate if definitions should be pushed.
# Usually, only the dev environment will push definitions. It is assumed that test/QA and
# prod environments will not push definitions but instead would rely on the Cafe promotion
# mechanism to promote the pushed definitions from dev to test/QA and prod environments.
CAFE_PUSH_DEFINITIONS=true - Save and exit from above file and redeploy the Assure and/or ER Application.
Verify the communication with DQ+
To verify the communication after above changes, go to your script home directory.
For Assure, that location is:
{Infogix_IA_install_home}\server-util\{IA_config_name}\IA\
For ER, that location is:
{Infogix_ER_install_home}\server-util\{ER_config_name}\ER\
And execute the cafeDefs script. The output should look like the following:
[websph1@pilot1 IA]$ /opt/Platform9.2/Infogix/server-util/IA/IA/cafeDefs.sh
java version "1.8.0_111"
Java(TM) SE Runtime Environment (build 1.8.0_111-b14)
Java HotSpot(TM) 64-Bit Server VM (build 25.111-b14, mixed mode)
Establishing all datastore definitions and pushing them to Data360.
Established 32 datastore definitions for Data360.
In DQ+ Pipelines, you will notice the Incoming icon which indicates Assure were able to make communication:
Comments
1 comment
Please note that "Sagacity" that is mentioned above is the previous product name for Data3Sixty DQ+.
Please sign in to leave a comment.