Unverified Commit 6c660b4f authored by marounkoussaifi's avatar marounkoussaifi Committed by GitHub
Browse files

Add Informatica documentation (#763)

* Add Informatica documentation
parent f608d4ea
......@@ -457,10 +457,10 @@ pa.scheduler.db.fetch.batch_size=50
#-------------------------------------------------------
# file containing variables which can be used in all workflows
pa.scheduler.global.variables.configuration=config/scheduler/global_variables.properties
pa.scheduler.global.variables.configuration=config/scheduler/global_variables.xml
# file containing generic information which can be used in all workflows
pa.scheduler.global.generic.info.configuration=config/scheduler/global_generic_info.properties
# refresh period, in minutes, for the global variables configuration
pa.scheduler.global.variables.refresh=10
#-------------------------------------------------------
#---------- EMAIL NOTIFICATION PROPERTIES ------------
......
......@@ -2780,6 +2780,10 @@ To enable email notifications see link:../admin/ProActiveAdminGuide.html#_get_no
include::./references/DataConnectors.adoc[]
== Application Connectors
include::./references/ApplicationConnectors.adoc[]
== Addons
......
The `application-connectors` bucket contains diverse generic application connectors for the most frequently used cloud data management systems (ERP, ETL, LDAP, Reporting and Monitoring, and ServiceNow). The aim of an application connector is to facilitate and simplify the integration of a cloud application in your workflows.
=== ETL
The ETL connectors allow connecting to data servers and benefit from their features.
The following presents the various ETL connectors that PWS handle.
==== Informatica
The Informatica workflow consists of one task.
*Variables:*
The Informatica workflow consists of a list of variables described in the following table.
.Informatica Connector variables
[cols="2,5,2,2,2,2"]
|===
| *Variable name* | *Description* | *Scope* | *Required?* | *Type* | *Default/Examples*
| `ENDPOINT`
| Server host.
| Workflow
| Yes
| String
| e.g. `https://xxx.informaticacloud.com/test/test`
| `USERNAME`
| Username to use for the authentication.
| Workflow
| No
| String
| e.g. toto
| `PASSWORD`
| Password to use for the authentication.
| Workflow
| No
| String
| e.g. toto
| `RESPONSE_FORMAT`
| Format of the server response .
| Task
| Yes
| string, json, xml, html, contentView
| json
| `RESPONSE_PATH`
| ...
| Task
| Yes
| String
| .
| `PARAM_var`
| Name of the api parameter (in case of multiple parameters, add several parameters fields).
| Task
| No
| String
| e.g. PARAM_input
| `HEADER_header`
| Name of the api request header (in case of multiple parameters, add several headers fields).
| Task
| No
| String
| e.g. HEADER_sessionId
| `JWT_TOKEN`
| JWT Token to use for the authentication.
| Workflow
| No
| String
| e.g. eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9
| `DEBUG`
| Allows printing more logs in the workflow results.
| Task
| Yes
| Boolean
| False
|===
*How to use this task:*
This WorkFlow performs a GET request to an Informatica API associated to an application already created by the Informatica user.
This workflow template supports the following authentication methods: a basic authentication using a username and a password, an advanced authentication using a JWT access token and finally an anonymous authentication where no authorization is required.
The authentication method is determined based on the definition of the parameters when launching the WF.
Supports Markdown
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment