Adeptia Inc.
Quick,Easy and Affordable Integration Software

ETL Suite

Downloads

Documentation

Compare Products

Next Step View Demo Ducumentation Free Download Contact Us
Newsletter Signup

Note:
- No SPAM, only Quarterly Newsletter.     - We respect your privacy, your email   will never be shared.
Product

Integration Questions


Q1. Which technologies are used to build the Adeptia Integration Suite ?
Ans1:- Adeptia Integration Suite is built using state-of-the-art technologies and open standards. It is a fully java-based product that leverages the J2EE architecture and framework. It utilizes XML, XSLT, Java (JMX, JDO, JCA, JMS etc.), Swing and Web services. XML is the core data format used in the integration component although the product supports a long list of disparate formats and structures. This product is not based on some older, proprietary message bus with a new front-end. It has been designed from the ground up to be a powerful integration Suite that resides in contemporary technology environments.

Q2. How does Adeptia Integration Suite facilitate data translation and transformation?
Ans2:- Adeptia Integration Suite leverages XML and XSL to translate incoming messages and data from the applications into an intermediate format that can be processed by the Integration Suite . This product allows Any-to-Any format conversion, application of mapping rules and transformation into any target format. All of this is made possible in a point-and-click, code-free approach.

Q3. How do users integrate their existing applications with Adeptia Integration Suite ?
Ans3:- Enterprise and external integration are the key strengths of the Integration Suite . Existing application can be integrated in a couple of ways depending on the needs of the project and the process flow that is being automated.

(1) Data-level integration is usually implemented in case of a scheduled or a batch-mode interface. This interface is deployed by leveraging direct access to the data layer of the application either by file import/export or by accessing the underlying database. For example, SAP IDOC interfaces (file based) and Siebel Interface tables (DB).

(2) API-level integration is implemented by either building or deploying a pre-built application adapter. These adapters provide real-time connectivity to the application functionality. This is deployed by using either JMS for message exchange, JCA for APIs, and Web Services client. For example, SAP BAPI interface.

Q4. Does Adeptia Integration Suite support SOAP?
Ans4:- Yes. SOAP is the envelope format for Web Services to provide a reliable messaging protocol for Adeptia Integration Suite Web Services.

Q5. Does Adeptia Integration Suite support Web Services?
Ans5:- Yes. Adeptia Integration Suite offers Web Services Consumer or client service.

Q6. Does Adeptia Integration Suite support file attachments?
Ans6:- Yes, Adeptia Integration Suite has the ability to handle ASCII and binary files data.

Q7. What versions of XML and MSXML does Adeptia Integration Suite use?
Ans7:- Adeptia Integration Suite supports standard XML documents, which support SAX2, DOM2, XSLT, and XPath.

Q8. What file formats are supported by Adeptia Integration Suite ?
Ans8:- Adeptia Integration Suite includes parsers and serializers for XML, XLS, flat files (delimited or positional), and EDI (ANSI X12 or UN/EDIFACT) documents.

Q9. What transport mechanisms does Adeptia Integration Suite support?
Ans9:- Adeptia Integration Suite supports HTTP, HTTPS, FTP, JMS SMTP, POP3, and file transports like LAN.

Q10. Does Adeptia Integration Suite include application adapters?
Ans10:- . No, Adeptia Integration Suite does not includes JCA adapters like SAP, PeopleSoft etc.

Q11. What security does Adeptia Integration Suite use?
Ans11:-Adeptia Integration Suite follows Java cryptography architecture. It uses data encryption/decryption algorithms, digital signature to secure data and send data through secure mode.

Q12. How messages are routed based on message content in Adeptia Integration Suite ?
Ans12:- Adeptia Integration Suite includes process designer to develop process definitions / flows, and activities or tasks that are attached to integration flows. These activities can include recursion, routing rules, triggers and timers, user-defined attributes with concurrence control.

Q13. Can users import existing DTD and XSD instances into Adeptia Integration Suite ?
Ans13:- A. Yes, the Adeptia Integration Suite can import existing Document Type Definition (DTD) or XSD, providing users the ability to leverage their existing investments. The Integration Suite supports external references inside a DTD and XSD. The Integration Suite supports namespaces on elements or element groups in schema.

Q14. What is included with Adeptia Integration Suite Messaging Services?
Ans14:- Adeptia Integration Suite includes Java Messaging Services (JMS) for receiving incoming documents, parsing the documents to determine their specific format, extracting key identifiers and identifying specific processing rules, delivering documents to their respective destinations. The Integration Suite also includes data mapping services, and services to ensure data integrity and security.

Q15. Does Adeptia Integration Suite store information in a repository?
Ans15:- Adeptia Integration Suite follows a store-and-forward architecture which means that all incoming data messages and files are stored and can be optionally archived. All information related to services, activities, process flows, business and data mapping rules are saved in a database along with detailed run-time information.

Q16. Can Adeptia Integration Suite import and use external XML, DTDs and Schemas?
Ans16:- . Yes, Adeptia Integration Suite can import and use external XML DTDs and Schemas. The Integration Suite uses XSLT to transform and modify the incoming XML data. With XSLT, any object model can be utilized to choose the DTD/Schema rather than enforce any one in particular. All that is required to interact with a legacy application is an appropriate two-way adapter to communicate to the applications API on one side and XML/HTTP or JMS on the other.