Enj Ports
Enj-Ports Is used to specify data interchange requirements, XML or file standards, frequency, instantiation, and business rules governing this data interchange. Enj-Ports follows water’s edge principle. It provides a capability for ‘docking’ applications to have access to a uniform ‘method’. Enj-Ports supports all the 3 possible data interchange strategies – Direct Database access, File exchange, Web Services. Enj-Ports has comprehensive features to handle both inbound and outbound, either in a synchronous or asynchronous fashion.
Enj works in conjunction with systems running in the enterprise. Third party interfaces are called Import, Export and Exim. These interfaces require to be defined for each distinct activity. Definitions include file locations, delimiters and file structures, labels and tags as well as the mapping each element is to have with corresponding Enj elements.
While in most cases, import and export are asynchronous, taking place based on a trigger from a predefined action, they can be easily configured to run in a synchronous mode taking care of fixed time batch runs to upload and download data. These synchronous activities take all the pain of integration out of system design, making the Enj system fully in mesh with all existing systems, providing the glue that your business needs to get various silos to work together, seamlessly and efficiently.
Import and Export can work with fixed file locations. At the same time they work equally well with email attachments, so there need not be any physical location sharing or networking, remarkably reducing integration costs over wide networks.
Needless to add, that Import and Export also handle Inter Process Communication (IPC) allowing information to flow seamlessly from one Enj process into another, making it extremely simple to deploy one process and then another, integrating it with the previous one easily and effectively.
Integration through Import and Export is so simple to implement that Enj can even be configured to work as a data warehouse, to get in and store data from a variety of distant client systems. The data so consolidated can be mined for various reporting needs discussed in depth in the monitoring module.
Enj works in conjunction with systems running in the enterprise. Third party interfaces are called Import, Export and Exim. These interfaces require to be defined for each distinct activity. Definitions include file locations, delimiters and file structures, labels and tags as well as the mapping each element is to have with corresponding Enj elements.
While in most cases, import and export are asynchronous, taking place based on a trigger from a predefined action, they can be easily configured to run in a synchronous mode taking care of fixed time batch runs to upload and download data. These synchronous activities take all the pain of integration out of system design, making the Enj system fully in mesh with all existing systems, providing the glue that your business needs to get various silos to work together, seamlessly and efficiently.
Import and Export can work with fixed file locations. At the same time they work equally well with email attachments, so there need not be any physical location sharing or networking, remarkably reducing integration costs over wide networks.
Needless to add, that Import and Export also handle Inter Process Communication (IPC) allowing information to flow seamlessly from one Enj process into another, making it extremely simple to deploy one process and then another, integrating it with the previous one easily and effectively.
Integration through Import and Export is so simple to implement that Enj can even be configured to work as a data warehouse, to get in and store data from a variety of distant client systems. The data so consolidated can be mined for various reporting needs discussed in depth in the monitoring module.