This project contains set of re-usable IICS Designs SDLC utilities, examples and documentations
- Informatica Cloud IPS Baseline Bundle
- Logging Framework
- Administration and Development Support Guides
- Process Templates and Examples
- Asset Management Scripts to export, import, publish and Version Control IPD Designs Implemented as Apache Ant Scripts
- Integration with other SDLC Assisting Tools (Migration/Transformation Tool, IICS Reporting Tool)
- Best practices and Other Integration use case Examples
- Read the provided documentation
- This bundle is continuously developed and improved, feel free to subscribe and monitor updates that might be useful for you in the future
- This bundle is not officially supported by Informatica, please report any issues you find via Github issues report
- Do not modify or move imported assets Project/Folder Locations after import, this would make updates much more difficult
- You can update or change imported resources to adjust them for your needs but keep in mind that it would be your responsibility to merge or maintain any changes you have made to provided designs
- Any of the provided assets can significantly re-designed or removed in the future releases
This should be the preferred method to build this package from source and deploy following a generic guide to use provided Asset Management Scripts
Using pre-build packages is easy but has some down-sides such as need to adjust a lot environment specific parameters after import i.e. Deployment targets for Connections and Processes Use build from source method which allows you to automate these adjustments in bulk using a declarative configuration and set of provided scripts
- Download pre built Distribution from [Releases]
- Use IICS-QuickStart-Bundle_InitialInstall_All_Designs.zip to initial install
- Use IICS-QuickStart-Bundle_Update_Excluding_Connections.zip to update your Bundle in environments whet it was already installed before
- Import Distribution Package Bundle
- Configure, adjust and publish provided designs
Design: Explore/Tools/Connections/AgentFileWriter.AI_CONNECTION.xml Description: Generic file writer allows to stage and upload files on Associated Secure Agent or group of Agents
This connection can be used to write files to Secure agent and is used by the SP-util-upload-agent process
Key Configuration property that might be your secure agent specific is File Connector/EventTargets/Directory
which is configured by default to /tmp directory. You also might want to create separate
Connections and corresponding process for each secure agent in case you need to push files to different agents.
Ideally One connection can be used and push of the files is done via any member of agent groups to shared
filesytem mounted to all members of the Secure Agent Group.
Design: Explore/DAS/DataAccessService.AI_CONNECTION.xml Description: DO NOT USE THIS SERVICE DIRECTLY is defined only to provide design time metadata definitions for Automated Steps execSQL and execMultiSQL
To configure this connection, just publish DataAccessService Connector and then DataAccessService Connection
Then You can publish corresponding Proxy processes (execMultiSQLProxy, execSQLProxy) that give access to DAS from Cloud guides and processes
Use Data Access Services/execMultiSQL or Data Access Services/execSQL to invoke data Access Service automated steps from IPD processes
Design: Explore/Tools/Connections/Email.AI_CONNECTION.xml Description: Shared Email Service to send alerts and notifications
Use Email Connection to send email notifications as an activity withing your Integration Processes
Github REST V3 APi to manage Gists see GIST API Documentation
This connector is useful to store and retrieve configurations, templates, snippets, etc. See an example of using Gist as a configuration storage provider Alert Service
Make sure your secure agents can access the GitHub API to store and retrieve the Alert Service configuration file.
This Alert Service Implementation can use Github Gist (both Cloud and On premise Github Enterprise Edition) as a storage for its configuration It is recommended to use private gist to store this configuration, you will need to create Security token to access private gists via API
-
Login to Github with an account that would be owner of the configurations (this should be likely service Account or account managed by IT Infrastructure administrators)
-
Go to Account Settings/Developer Settings/Personal access tokens
-
Create new token and give it descriptive name such as
IICS-Configuration-Gist-Access -
Select only gist permission
-
Capture generated token and save it in a save location for later use in the Service Connector configuration after Deployment of the IICS package
Connector Properties
| Name | Description |
|---|---|
| access_token | Gist API Access Token |
| api_version | API Version (currently V3) |
| base_uri | Base URI of the REST endpoint Base URI of the REST endpoint https://api.github.com |
Provides Support to store and retrieve configurations or other files as GitLab Snippets See Gitlab API Documentation
Make sure your secure agents can access the GitLab API to store and retrieve the Alert Service configuration file.
This Alert Service Implementation can use Cloud Hosted or on-premise GitLab as a storage for its configuration It is recommended to use private snippets to store this configuration, you will need to create Security token to access private Assets via API
-
Login to GitLab with an account that would be owner of the configurations (this should be likely service Account or account managed by IT Infrastructure administrators)
-
Create new token and give it descriptive name such as
IICS-Configuration-API-Access -
Optionally set expiration date
-
Select api access permission
-
Capture generated Token and use it to configure GitLab Service Connector
Connector Properties
| Name | Description |
|---|---|
| base_uri | GitLab API Base URL (example: https://gitlab.example.com/api) |
| access_token | API Access Token |
| api_version | API Version (currently v4) |
This service defines actions to connect to IICS through REST API and perform Export/Import and license management activities
Database Used to Store Simple key/value configurations
This Connection provides ability to store configurations in External Database and Guides/processes to manage such configurations
Design: Explore/Logging/Connections/IPaaS-Logging.AI_CONNECTION.xml Description: IPaaS Database for Logging and job tracking
| Term | Description |
|---|---|
| API | Application Programming Interface |
| Application Integration Console | ICAI Cloud and Secure Agent Runtime Administration Tool |
| BPEL | Business Process Execution Language |
| BPMN | Business Process Modeling Notation |
| DAS | Data Access Service |
| ICAI | (formerly ICRT) Informatica Cloud Application Integration, see ICRT |
| ICDI | (formerly ICS) Informatica Cloud Data Integration is an ETL batch integration component of IICS platform |
| IICS | Informatica Intelligent Cloud Services, Informatica Cloud Integration platform |
| IPD | Informatica Process Designer |
| Informatica Secure Agent | Informatica Data Integration Execution Agent that Provides ability to integrate data on premise and in the Cloud, hybrid data integration both batch and real time |
| REST | REpresentational State Transfer |
| SDLC | Software Development Lifecycle |
| WSDL | Web Service Definition Language |