Basic Architecture for Informatica Product 360

The above diagram is self explanatory. I put some cloud components for data export operation. This is a plain and simple way to manage your product data from various source system residing in various other systems.

Now, Cloud Function, Cloud CDN and Apigee API platform is just examples of doing the operations. Similar functionality is available if you’re going to use IICP (Informatica Intelligent Cloud Platform). Also, Data lake can be replaced by more sofisiticated Snowflake. Extra 3RD Party API Management is widely distributed between different software and services.

Task translation could be automated using REST API inbound and outbound calls, although in a real-time scenario, once the system is loaded by the translated text, a separate Workflow engine will be trigged for one or more level of approval. ActiveVOS is the BPEL engine for P360 and can be widely used for the purpose of Task management.

Image generation and linking could be managed by 3rd party however, upload and linking the several other types of images to the products in P360 is carried out by IMM (Informatica Media Manager).

Once everything is done, export operation will be triggering various forms (determined by channels) resulting RAW text file (JSON/TXT/XML) along with images in ZIP stored in exported folder.

We can use Cloud function or any other utility to trigger a Data Pipeline henceforth which will eventually send the data to respective systems.

--

--

Get the Medium app

A button that says 'Download on the App Store', and if clicked it will lead you to the iOS App store
A button that says 'Get it on, Google Play', and if clicked it will lead you to the Google Play store
Biswarup Ghoshal

Biswarup Ghoshal

Senior MDM Architect | Cloud Compute Enthusiasts