Informatica Overview
Informatica
Informatica as tool has emerged out to
be one of the finest tools in the ETL domain across the globe. Many
organisations are currently implementing because of it's wider span of playing
the role of working as Integration tool also.
Informatica Data
Transformation - DT
Data Format Transformation Libraries :
Informatica DT Process Flow
XML has structured data. Eg; Defined
parent – child relationship among tags.
Informatica B2B Data Exchange (DX)
For example, you create a workflow to
process EDI documents for two partners. One partner requires acknowledgement and
the other does not. You can create a profile for the first partner to use the
workflow to process EDI documents. Set up parameters for the profile to allow
for document acknowledgement. Then create a profile for the second partner to
use the same workflow to process EDI documents but without acknowledgment. In
this way, you can customize the way a workflow is used to process documents for
each partner.
Workflows
A B2B Data Exchange workflow represents
a Power Center workflow. You must create a workflow in the B2B Data Exchange
Operation Console for every Power Center workflow that processes B2B Data
Exchange documents.
Batch Workflow
Process:
Partner:
Account:
Profiles
—
Informatica
Informatica as tool has emerged out to
be one of the finest tools in the ETL domain across the globe. Many
organisations are currently implementing because of it's wider span of playing
the role of working as Integration tool also.
Informatica is an easy to use tool with basically less coding required. Informatica has variants
like Power Center , Data Quality , Data Transformation, Data Exchange etc. All
these tools have UI based drag and drop working or Component selection working.
In tools like Power Center and IDQ we can have various transformations
that can be chosen by dragging them to the Transformation Pane. While in tools
like Informatica DT or Informatica B2B Data Exchange we have various options of
components choosing based on our requirements.
Informatica Data
Transformation - DT
Informatica DT has been incorporated in
order to provide conversion of any format of data to any
format. Informatica Data Transformation is enterprise-class software for
extracting data from any file, document, or message—regardless of format,
complexity, or size—and transforming it into a usable form. Informatica
B2B Data Transformation includes the most comprehensive out-of-the-box support
for industry standard message formats such as EDI, SWIFT.
Data Format Transformation Libraries :
These libraries leverage the broadest set of prebuilt transformations on
the market, including a wide variety of industry-standard formats (such as
SWIFT, HL7, EDI X12, EDIFACT, and others) document formats (such as Word,
Excel, PDF and HTML), and flat files (positional, non positional, variant
files, and undocumented binaries). Some legacy formats, such as COBOL, are also
supported.
Informatica DT Process Flow
Why XML?
XML has structured data. Eg; Defined
parent – child relationship among tags.
XML can be validated and based on it it
can be categorized as Well –formed and Valid Documents
XML provides a common platform for all
formats' conversion and DT enables the conversion for this.The conversion
process requires a well defined XSDs with which XML confronts.Elements
Hierarchy , Occurrences, Relationship all are well defined in this XSDs.
You can get information about XML from
many books, articles, or web sites. For an excellent tutorial, see http://www.w3schools.com
Informatica B2B Data Exchange (DX)
B2B Data Exchange facilitates the
transfer and processing of structured and unstructured documents for trading
partners. You can use B2B Data Exchange to manage the flow and
transformation of documents and to manage the trading partners that send and
receive the documents.Use B2B Data Exchange to customize the processing of
similar types of documents using the same transformation logic for different
trading partners. You create workflows that define the transformation logic to
process different types of documents. Then, create a profile to associate a
partner with a workflow and define the document processing requirements
for the partner.
For example, you create a workflow to
process EDI documents for two partners. One partner requires acknowledgement and
the other does not. You can create a profile for the first partner to use the
workflow to process EDI documents. Set up parameters for the profile to allow
for document acknowledgement. Then create a profile for the second partner to
use the same workflow to process EDI documents but without acknowledgment. In
this way, you can customize the way a workflow is used to process documents for
each partner.
B2B Data Exchange uses the Data
Transformation Engine to convert documents from one format to another. You can
include Unstructured Data transformations in the Power Center workflows you
build to process Data Exchange documents.
Workflows
A B2B Data Exchange workflow represents
a Power Center workflow. You must create a workflow in the B2B Data Exchange
Operation Console for every Power Center workflow that processes B2B Data
Exchange documents.
After you create a Power Center workflow
to process Data Exchange documents, you export the mapping. Use the mapping
export file as the workflow definition file for the workflow that represents
the Power Center workflow.
Batch Workflow
Use batch workflows for documents that you generate or process
infrequently, for example, once a day or less. These are defined in power
center.
A batch workflow that processes a
single document is more efficient than a real-time workflow that processes the
same document. Real-time workflows run continuously and consume more Power
Center system resources.
Process:
1. One of the following events occurs:
ü
A scheduled event occurs.
ü
An input file arrives.
ü
A condition defined in a monitor is
satisfied.
ü
The operator starts the batch workflow.
2. B2B Data Exchange runs the batch
workflow.
3. B2B Data Exchange creates a new
event and assigns Pending status to the event.
4. If an input file causes the workflow
to run, B2B Data Exchange saves the input file as a temporary file in the
document store.
5. The system calls Power Center Web
Services to initiate the batch workflow. The system passes the event ID, event
context, and workflow parameters to the Power Center mapping. If an input file
causes the workflow to run, the batch workflow also passes the location of the
file.
6. The workflow runs its defined tasks.
Partner:
Partners are the entities that send
documents to B2B Data Exchange for processing and receive the processed
documents in return. A partner can be an organization like a vendor or
customer.
Setting, searching, editing , deleting,
adding an account are the functions that can be done with te help of
Partner.
Partner Promotion:
Partner promotion enables you to export
one or more partners and their related entities from one environment to another.
For example, you can promote partners from development to test or from test to
production
After you create and test a partner and
its associated entities in the test environment you can flag it as "Ready
to be promoted" on the Update Partner screen. You can later search for all
the partners that you marked and export them all at once.
The partner export process creates a
file of partners to be exported as well as partners and entities associated
with the partners.
Exporting Partners:
We can export an already created
partner with selection option of all partners or single partner.
Account:
Account Uniqueness
The dx.system.account.uniqueness system
property indicates whether an account is unique within the scope of the partner
or within the scope of B2B Data Exchange.
If the dx.system.account.uniqueness
system property is set to PARTNER, the account is unique within the scope of
the partner. You can assign the same account number to multiple partners. If
you do, the B2B Data Exchange.
Server determines the profile based on
the application, partner, and account number.
If the dx.system.account.uniqueness
system property is set to SYSTEM, the account is unique within the scope of B2B
Data Exchange and you cannot use the same account number more than once. Also
the B2B Data Exchange Server determines
the profile based on the application and account number.
Profiles
Profiles enable you to associate a
workflow with a partner or an account. A profile defines how to process a
document for a partner or an account. It also defines the properties that
customize that workflow to process documents for the associated partner or
account. A profile associates a workflow to a partner or account.
Profile ID
The profile ID uniquely identifies a
profile. When you create a profile, the B2B Data Exchange Server generates and
sets the profile ID. When you import a profile into another instance of B2B
Data Exchange, the B2B Data Exchange Server of the new instance generates a new
profile ID for the imported profile. The imported profile ID can differ from
the original profile ID.
For example, when you move a profile
from a development environment of B2B Data Exchange to a production
environment, the production instance generates a profile ID. For this reason,
if you develop and test workflows in a development environment and then move
them to a production environment, use the $profileName variable instead of the
$profileId to associate between a partner and workflow.
Categories:
You can restrict access to partners,
accounts, and profiles with categories.
When you assign categories to objects,
you also restrict access to related objects, such as events, endpoints, and SLA
rules. The B2B Data Exchange administrator assigns categories to user groups to
determine which users can access the objects.
PREV NEXT
—
Comments
Post a Comment