FAQs
General Questions
What is Psyncopate TIBCO Modernization Suite?
It is a suite of tools that automate the migration from TIBCO® to Confluent®, significantly reducing manual effort and minimizing errors.
What level of effort reduction can be expected by using these accelerators?
Users can save up to 50% in engineering time, effort, and costs compared to manual migration processes.
How do I access the tool?
The tool is accessible via a web browser. Users can log in using their credentials.
How do I update the tool?
Updates are released periodically; no manual installation is required for this web-based app.
Can I use the tool offline?
No, the tool is web-based and cannot be used offline.
How much time does it take to migrate a project?
The time taken to migrate a project depends on the project size and complexity. Smaller projects can be migrated in a few minutes, while larger projects may take a few hours.
Can I migrate multiple projects simultaneously?
Yes, users can migrate multiple projects simultaneously.
Can I delete a project after migration?
Yes, users can delete a project after migration.
Can I restore deleted projects?
Yes, deleted projects can be restored from the trash option in the profile section.
What are the roles available in the suite? What is the difference between them?
The tool has three roles: super admin, admin, and user. The super admin has access to all projects and can manage user roles and permissions. Admins have access to all projects, while users can access only their projects.
How can I request an admin or super admin role?
To request an admin role, contact your super admin. For a super admin role, email acclsupport@psyncopate.com.
How can I get support, request a new feature, or inquire about a subscription?
Please reach out to acclsupport@psyncopate.com.
Kafka Config Generator
What are Flink jobs? Why are we considering creating a Flink_Jobs.sql file?
Flink jobs are data processing pipelines used for real-time stream processing in Confluent platform. The Flink_Jobs.sql file is included in the migration to support stream processing requirements.
Why are there two output files, YAML and shell script files, for topic creation?
YAML file: YAML file(s) can be deployed on Confluent For Kubernetes (CFK) platform to create Kafka® topics in bulk.
Shell script: Shell scripts can be executed on Confluent CLI platform to create topics in bulk.
Which files are used to generate flink jobs?
bridges.conf and tibemsd.conf files are used to generate flink jobs.
Does Kafka Config Generator migrate all topics from TIBCO?
Yes, it migrates all topics.
What messaging systems are supported by the Kafka Config Generator?
It supports TIBCO EMS, JMS, IBM MQ, ActiveMQ, and RabbitMQ.
Schema Converter
What is the difference between XSD and Avro schema files?
XSD files define the structure and validation rules for XML documents, while Avro™ schema files define the structure and data types for serialized data in the Avro format.
What is the root file in XSD?
- The root file in XSD is the primary XML Schema Definition file that defines the structure, data types, and validation rules for an XML document.
- It ensures XML documents follow a predefined structure and validation rules.
How is an XSD file considered the root file?
- An XSD file is considered a root file if it is not included or imported in any other XSD.
- It contains the
<xs:schema>element and defines the structure of the XML.
How is a root element defined in an XSD file?
A root element is defined using the <xs:element> tag directly under the <xs:schema> element.
Example:
<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema"><xs:element name="rootElement"> <xs:complexType> <xs:sequence> <xs:element name="childElement" type="xs:string"/> </xs:sequence> </xs:complexType></xs:element></xs:schema>Why does the count of output XSDs differ from the input?
The Schema Converter consolidates all XSDs (both root and child) into a single Avro schema, resulting in the change in the number of output files.
What is the purpose of the lineage section in the Schema Converter?
The lineage section displays the hierarchy of a root XSD and its referenced child XSDs in a hierarchical format, aiding in understanding the relationships between XSD files.
How can I view the lineage section?
Users can view the lineage section in the Schema Converter output by clicking on the “View” action.
What is the usage section in the Schema Converter?
The usage section displays all .process files that reference the current XSD, providing insights into the XSD’s usage across the project.
How can I download the lineage and usage sections?
Users can download the lineage and usage sections as .yml and .csv files, respectively, for further analysis.
Where can I deploy the Avro schema files?
The Avro schema files can be deployed in the Confluent platform for data serialization and interoperability.
How can I handle schema evolution with Avro schema files?
Handle schema evolution by following the Avro schema evolution guidelines, such as adding optional fields, renaming fields, and handling backward and forward compatibility.
XSLT Converter
What is the purpose of the XSLT Converter?
The XSLT Converter transforms TIBCO XSLT files into standard XSLT files, ensuring compatibility with other systems.
How does the XSLT Converter identify XSL content in the project?
The XSLT Converter identifies XSL content by parsing the process files. It creates an XSLT for each input and return binding available in the process files of the given project.
What is the difference between TIBCO XSLT and standard XSLT?
TIBCO XSLT includes proprietary functions and extensions that are not part of the standard XSLT specification.
How can I compare the original and converted XSL files?
Users can compare the original and converted XSL files by clicking on the “Show Difference” action, which highlights the differences between the two files.
How can I validate the transformation of an XML file?
Users can validate the transformation of an XML file by comparing the output of the converted XSL transformation with the output of the original TIBCO XSLT transformation.
How can I transform an XML file using the converted XSL?
Users can transform an XML file using the converted XSL by uploading the XML file using “Transform” action from “XML Transformer” tab and validating the transformation against the original TIBCO XSLT transformation.
How can I handle custom functions in the XSLT Converter?
Custom functions in the XSLT Converter require manual implementation as they do not have a native equivalent in the standard XSLT library.
How can I use the converted XSL files for transformation?
Users can use the converted XSL files for transforming XML files across various environments by referencing the appropriate libraries, such as Saxon and Xalan.
How can I ensure compatibility with other systems using the converted XSL files?
Ensure compatibility with other systems by following the standard XSLT specification and handling custom and dependent functions manually.
Connector Config Generator
Why are some connections failing?
The input file may be missing mandatory connection parameters.
Why are some connections missing?
The necessary files are not found in the input project.
How should I provide file paths when required?
Download the relevant files to the local storage and provide the paths in the required placeholders.
Why do we use a subquery for custom queries in the Confluent JDBC Source Connector?
We use a subquery in custom queries to avoid syntax errors caused by multiple WHERE clauses. The Confluent platform appends its own WHERE clause, and if your query already has one, it can lead to conflicts. By structuring the query with a subquery, we ensure compatibility and prevent errors, allowing for smooth data retrieval.
-- Original query that retrieves regular customersSELECT *FROM connector.customer_detailsWHERE customer_type = 'Regular';
-- Attempting to append another WHERE clause directly leads to a syntax errorSELECT *FROM connector.customer_detailsWHERE customer_type = 'Regular'WHERE "customer_id" > ? -- Syntax error: multiple WHERE clauses not allowed
-- Correct approach using a subquery to avoid syntax errorsSELECT * FROM ( SELECT * FROM connector.customer_details WHERE customer_type = 'Regular' -- Original filtering condition)WHERE "customer_id" > ? -- Safe to append additional condition hereORDER BY "customer_id" ASC;What happens when using transforms.ReplaceField.include in the JDBC Sink Connector?
The fields listed in this property retain their original names in the sink destination.
How can I view Confluent Connector logs when using CFK?
Run the following command:
kubectl logs connect-0 --since=5mHow do I upload an HTTPS certificate for Confluent connectors?
Upload the certificate to your Confluent cloud platform. You can verify the same in the Confluent connector JSON file.
Example command:
kubectl cp custom-truststore.jks confluent/connect-0:/home/appuserMapping Documents
What is the purpose of the Mapping Documents tool?
The Mapping Documents tool generates detailed mapping and requirement documentation for TIBCO processes and activities, including usage, transitions, activity types, field mappings, use cases, and complexity metrics.
What is a complexity template? Is it user-specific?
A complexity template defines the complexity of a process or sub-process based on user-defined criteria. Except for the default template, all templates are user-specific.
Can I update a template after creating it?
No, existing templates cannot be updated once created.
How many complexity templates can be created?
Users can create multiple templates based on their requirements and reuse them as needed.
What is an active process or sub-process?
A process or sub-process which is used in any use case is considered as an active process or sub-process.
API Code Generator
What is the purpose of this accelerator?
It simplifies modernizing legacy TIBCO APIs and services by generating production-ready code that customers can deploy on any modern cloud service.
What are the key benefits of using this accelerator?
It accelerates time-to-market by reducing redevelopment time and manual errors while offering flexible, multi-language API code that adapts to a range of deployment environments.
Which API transformations are supported?
The tool supports SOAP-to-SOAP, REST-to-REST, and SOAP-to-REST conversions.
In which programming languages is the API code generated?
It produces implementation-ready API code in Java (Spring Boot), Python (Uvicorn), and C#.
What input does the accelerator require?
It accepts TIBCO project file(s), such as a ZIP archive containing the necessary project definitions.
What is included in the generated output?
The output is a single ZIP file containing structured API projects, categorized by transformation type and implementation language.
Where can these API projects be deployed?
The API projects are deployable on any modern cloud or on-premises platform, including AWS/EKS, Azure/AKS, Google Cloud/GKE, OpenShift, and Kubernetes.
TIBCO® is a registered trademark of Cloud Software Group, Inc. and/or its subsidiaries in the United States and/or other countries. Confluent® is a registered trademark of Confluent, Inc. Kafka® is a registered trademark and Avro™ is a trademark of the Apache Software Foundation. All other product names, logos, and brands are the property of their respective owners.