Initial commit

CONTRIBUTING.md

@@ -0,0 +1,19 @@
+# How to Contribute
+
+We'd love to accept your patches and contributions to this project. There are
+just a few small guidelines you need to follow.
+
+## Contributor License Agreement
+
+Contributions to this project must be accompanied by a signed
+[Contributor Agreement](ContributorAgreement.txt).
+You (or your employer) retain the copyright to your contribution,
+this simply gives us permission to use and redistribute your contributions as
+part of the project.
+
+## Code reviews
+
+All submissions, including submissions by project members, require review. We
+use GitHub pull requests for this purpose. Consult
+[GitHub Help](https://help.github.com/articles/about-pull-requests/) for more
+information on using pull requests.

ContributorAgreement.txt

@@ -0,0 +1,56 @@
+Contributor Agreement
+
+Version 1.1
+
+Contributions to this software are accepted only when they are
+properly accompanied by a Contributor Agreement. The Contributor
+Agreement for this software is the Developer's Certificate of Origin
+1.1 (DCO) as provided with and required for accepting contributions
+to the Linux kernel.
+
+In each contribution proposed to be included in this software, the
+developer must include a "sign-off" that denotes consent to the
+terms of the Developer's Certificate of Origin.  The sign-off is
+a line of text in the description that accompanies the change,
+certifying that you have the right to provide the contribution
+to be included.  For changes provided in source code control (for
+example, via a Git pull request) the sign-off must be included in
+the commit message in source code control.  For changes provided
+in email or issue tracking, the sign-off must be included in the
+email or the issue, and the sign-off will be incorporated into the
+permanent commit message if the contribution is accepted into the
+official source code.
+
+If you can certify the below:
+
+        Developer's Certificate of Origin 1.1
+
+        By making a contribution to this project, I certify that:
+
+        (a) The contribution was created in whole or in part by me and I
+            have the right to submit it under the open source license
+            indicated in the file; or
+
+        (b) The contribution is based upon previous work that, to the best
+            of my knowledge, is covered under an appropriate open source
+            license and I have the right under that license to submit that
+            work with modifications, whether created in whole or in part
+            by me, under the same open source license (unless I am
+            permitted to submit under a different license), as indicated
+            in the file; or
+
+        (c) The contribution was provided directly to me by some other
+            person who certified (a), (b) or (c) and I have not modified
+            it.
+
+        (d) I understand and agree that this project and the contribution
+            are public and that a record of the contribution (including all
+            personal information I submit with it, including my sign-off) is
+            maintained indefinitely and may be redistributed consistent with
+            this project or the open source license(s) involved.
+
+then you just add a line saying
+
+        Signed-off-by: Random J Developer <[email protected]>
+
+using your real name (sorry, no pseudonyms or anonymous contributions.)

LICENSE

@@ -1,3 +1,4 @@
+
                                  Apache License
                            Version 2.0, January 2004
                         http://www.apache.org/licenses/
@@ -172,7 +173,7 @@
       defend, and hold each Contributor harmless for any liability
       incurred by, or claims asserted against, such Contributor by reason
       of your accepting any such warranty or additional liability.
-
+  
    END OF TERMS AND CONDITIONS
 
    APPENDIX: How to apply the Apache License to your work.

README.md

@@ -1,2 +1,80 @@
-# ci360-extensions
-This repository contains a number of connectors and agents that are ready to be used to enhance the capabilities of CI360 and connect to 3rd party services.
+# SAS Customer Intelligence 360 - Extensions
+
+
+## Overview
+SAS CI360 Connector Framework and Agent SDK provide infrastructure to integrate CI360 applications with other applications. This repository contains a number of connectors and agents that are ready to be used to enhance the capabilities of CI360 and connect to 3rd party services. In addition, there are other integration assets included as well. All integration assets included in this repository are listed below, with short description. Details about each are included within specific sub-folders.
+
+## Table of Contents
+
+This topic contains the following sections:
+* <a href="#prerequisites">Prerequisites</a>
+* <a href="#installation">Installation</a>
+* <a href="#list">List of Extensions</a>
+* <a href="#getstart">Getting Started</a>
+* <a href="#contributing">Contributing</a>
+* <a href="#license">License</a>
+* <a href="#resources">Additional Resources</a>
+
+## Prerequisites
+
+Prerequisites vary between integration assets included here, and are listed in detail for each in the respecitive sub-folders. But some of the prerequisites include:
+- Amazon Web Service account with access to Lambda and API Gateway service
+- Microsoft Azure account with access to Functions and other Azure services
+- Java 1.8 or newer
+- Python 3.7 or newer
+
+## Installation
+
+Installation instructions for every extension are included in the project specific sub-folder README file. Installation and deployment instructions are platform specific.
+
+## List of Extensions
+
+This is a list of connectors and agents included in this repository:
+- [__ci360-scg-agent__](ci360-scg-agent): Syniverse Communication Gateway (SCG) agent, enables SMS/MMS/WhatsApp through Syniverse
+- [__ci360-scg-connector__](ci360-scg-connector): Syniverse Communication Gateway (SCG) connector, enables SMS/MMS/WhatsApp through Syniverse
+- [__ci360-sfmc-connector__](ci360-sfmc-connector): Salesforce Marketing Cloud (SFMC) connector, enables Email and SMS through Salesforce
+
+## Getting Started
+
+To set up and use the sample connector codes you need to perform the following steps :
+
+### Download sample connector code
+1. Download a `ci360-extensions` project source code into zip/tar.gz/tar.bz2/tar file format on your local machine.<br/>
+   `Note:` You can also clone the project on your local machine
+
+2. The project will be downloaded on your local machine in your specified file format. You need to unzip/untar the downloaded project.  
+
+3. You can see the folder `ci360-extensions` after unzip/untar the project.
+
+4. Open the `ci360-extensions` folder. It will contain multiple sub-folders for various connector and agent integration resources.
+
+### Build or Deploy
+Build and deployment instructions are included for each of the integration assets in their respoective sub-folders.
+
+### Deploying CI360 Connectors
+Please refer [Set up a Custom Connector](https://go.documentation.sas.com/doc/en/cintcdc/production.a/cintag/ext-connectors-custom.htm) section in SAS Customer Intelligence 360 admin guide.
+
+### Register your connector into CI360
+
+For most connector or agent integration assets, you need to register the connector and endpoint with these details into the CI360 system to use the connector. Details are included for each connector or agent in their sub-folders. Documentation sections are referenced below for eacy access.
+
+**Add and Register a Connector**
+Please refer to [`Add and Register a Connector`](https://go.documentation.sas.com/doc/en/cintcdc/production.a/cintag/ext-connectors-add.htm) in SAS Customer Intelligence 360 admin guide.
+
+**Add an Endpoint**
+Please refer to [`Add an Endpoint`](https://go.documentation.sas.com/doc/en/cintcdc/production.a/cintag/ext-connectors-add-endpoint.htm) in SAS Customer Intelligence 360 admin guide.
+
+
+## Contributing
+
+> We welcome your contributions! Please read [CONTRIBUTING.md](CONTRIBUTING.md) for details on how to submit contributions to this project. 
+
+
+## License
+
+> This project is licensed under the [Apache 2.0 License](LICENSE).
+
+
+## Additional Resources
+
+For more information, see [External Data Integration with Connectors](http://documentation.sas.com/?cdcId=cintcdc&cdcVersion=production.a&docsetId=cintag&docsetTarget=ext-connectors-manage.htm&locale=en#p0uwf5nm4rrkn1n1gwrm03rh911r).

SUPPORT.md

@@ -0,0 +1,3 @@
+## Support
+
+We use GitHub for tracking bugs and feature requests. Please submit a GitHub issue or pull request for support.

ci360-scg-agent/.classpath

@@ -0,0 +1,23 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<classpath>
+	<classpathentry kind="src" output="target/classes" path="src/main/java">
+		<attributes>
+			<attribute name="optional" value="true"/>
+			<attribute name="maven.pomderived" value="true"/>
+		</attributes>
+	</classpathentry>
+	<classpathentry kind="src" output="target/test-classes" path="src/test/java">
+		<attributes>
+			<attribute name="test" value="true"/>
+			<attribute name="optional" value="true"/>
+			<attribute name="maven.pomderived" value="true"/>
+		</attributes>
+	</classpathentry>
+	<classpathentry kind="con" path="org.eclipse.m2e.MAVEN2_CLASSPATH_CONTAINER">
+		<attributes>
+			<attribute name="maven.pomderived" value="true"/>
+		</attributes>
+	</classpathentry>
+	<classpathentry kind="con" path="org.eclipse.jdt.launching.JRE_CONTAINER"/>
+	<classpathentry kind="output" path="target/classes"/>
+</classpath>

ci360-scg-agent/.gitignore

@@ -0,0 +1,8 @@
+/cacheData
+/target/
+target/
+*.log
+*.zip
+logs/
+/logs/*
+/last_event_json.txt

ci360-scg-agent/.gitlab-ci.yml

@@ -0,0 +1,20 @@
+image: maven:latest
+
+variables:
+  MAVEN_CLI_OPTS: "--batch-mode --errors --fail-at-end --show-version"
+  MAVEN_OPTS: "-Dmaven.repo.local=.m2/repository"
+
+cache:
+  paths:
+    - .m2/repository/
+    - target/
+
+build:
+  stage: build
+  script:
+    - mvn $MAVEN_CLI_OPTS compile
+
+test:
+  stage: test
+  script:
+    - mvn $MAVEN_CLI_OPTS test

ci360-scg-agent/.project

@@ -0,0 +1,23 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<projectDescription>
+	<name>ci360-scg-agent</name>
+	<comment></comment>
+	<projects>
+	</projects>
+	<buildSpec>
+		<buildCommand>
+			<name>org.eclipse.jdt.core.javabuilder</name>
+			<arguments>
+			</arguments>
+		</buildCommand>
+		<buildCommand>
+			<name>org.eclipse.m2e.core.maven2Builder</name>
+			<arguments>
+			</arguments>
+		</buildCommand>
+	</buildSpec>
+	<natures>
+		<nature>org.eclipse.jdt.core.javanature</nature>
+		<nature>org.eclipse.m2e.core.maven2Nature</nature>
+	</natures>
+</projectDescription>

ci360-scg-agent/.settings/org.eclipse.core.resources.prefs

@@ -0,0 +1,4 @@
+eclipse.preferences.version=1
+encoding//src/main/java=UTF-8
+encoding//src/test/java=UTF-8
+encoding/<project>=UTF-8

ci360-scg-agent/.settings/org.eclipse.jdt.core.prefs

@@ -0,0 +1,6 @@
+eclipse.preferences.version=1
+org.eclipse.jdt.core.compiler.codegen.targetPlatform=1.8
+org.eclipse.jdt.core.compiler.compliance=1.8
+org.eclipse.jdt.core.compiler.problem.forbiddenReference=warning
+org.eclipse.jdt.core.compiler.release=disabled
+org.eclipse.jdt.core.compiler.source=1.8

ci360-scg-agent/.settings/org.eclipse.m2e.core.prefs

@@ -0,0 +1,4 @@
+activeProfiles=
+eclipse.preferences.version=1
+resolveWorkspaceProjects=true
+version=1

ci360-scg-agent/Dockerfile

@@ -0,0 +1,18 @@
+FROM openjdk:8-jre-alpine
+LABEL version="${project.version}"
+LABEL author="Bojan Belovic"
+LABEL company="SAS Institute"
+# build arguments
+ARG VERSION=${project.version}
+# copy app into image
+COPY . /opt/ci360-scg-agent/
+# just dir output for debug
+# RUN ls -la /opt/ci360-scg-agent/*
+# set working dir
+WORKDIR /opt/ci360-scg-agent
+# Inform Docker that the container is listening on the specified port at runtime
+EXPOSE 8080
+# set HEALTHCHECK
+HEALTHCHECK CMD ps -ef | grep java | grep ci360-scg-agent
+# run application with this command line
+ENTRYPOINT ["java", "-Dlogback.configurationFile=logback.xml", "-DconfigFile=agent.config", "-Xms16m", "-Xmx256m", "-jar", "ci360-scg-agent-${project.version}.jar"]