You are viewing an old version of this page. View the current version.
Frequently Asked Questions
Q: How does an administrator address production deployment and rollback of jobs?
A: Deploy from "Jitterpak" and previous versions.
Q: Is automated migration from a test environment to Production available?
A: A customer’s Jitterbit administrator is responsible for moving projects from Test to Production in adherence with the customer’s promotion guidelines. It is possible to deploy a Jitterpak from a command line into a new environment.
Q: Can all areas of the configuration be automated, or are there some that must be done through the UI?
A: We believe the only action that cannot be automated, is creating a user. No audit function has been automated. The user should be able to automate anything using our web API.
Q: What is your recommended backup and restore procedure?
A: We have several options, but the quickest way to recover is to create a Backup of the Jitterpak. Projects are automatically backed up to the cloud. Recovery would require installing the software again and logging in with the same account. The projects would automatically download again.
Q: Is a built-in Scheduler provided?
Q: Does your product include a dashboard performance interface?
A: Yes. The Web Management Console provides full visibility into the state of the operational run times of integrations.
Q: Does Jitterbit provide for Data Partitioning?
A: Jitterbit can partition data if the designer employs filters on the input stream to partition the data. Jitterbit currently does not provide automatic data partitioning in the traditional sense.
Q: What are the data replication capabilities provided?
A: Data replication can be designed with Jitterbit for any 2 systems.
Q: Does your product require its own database for configuration settings, logs or other product functions? If so, which DB (MS SQL, MySQL, Oracle, DB2)?
A: Yes. By default, Jitterbit does install a PostgreSQL DB on the Jitterbit Server or Jitterbit Local Agents. It is used to store metadata about the integrations and does not require a DB administrator to manage it. We can also use SQLite for the database.
Q: Diagram on the flow of data through major application components and an indication of which servers/agents they reside on.
A: The Jitterbit platform consists of a single server/agent that enables integration with an unlimited number of endpoints (application connections). Integration designers use the Jitterbit Studio on their workstations to design, deploy and manage integrations processed on the server/agent.The "flow" of data between applications always goes though the Jitterbit Server/Agent.
Q: Does Jitterbit provide on-demand data integration? Can you publish an ETL process and/or target attribute as a Web Service? Describe any other means by which your solution might be externally instantiated.
A: Yes, Jitterbit provides SOAP and REST web services, and command line calls.
Q: Does Jitterbit support external monitoring using SNMP, REST, or SQL (if state is held in DB)?
A: Yes. External monitoring can be done with REST and access to the database. We do NOT support SNMP.
Q: How are temporary files handled? Are they cleaned automatically? If so, how often?
A: Jitterbit Design Studio Client: Yes. The location of temporary files will be C:\Windows\Temp\jitterbit_client. These files will never take up much space and they are cleaned automatically. The only exception is if the application is terminated from the task manager.
Server/Local Agents: Yes. The default location of the temporary files is \tmp, or on Windows it is c:\windows\temp. There is also a folder used for debugging located …\Jitterbit Integration Server\DataInterchange\Temp. The schedule to clean temporary files is controlled by CleanupRules.xml.
Q: How do schedule-based initiation and event-based initiation of jobs work?
A: Built-in scheduler to be used from Windows or Linux; from command line, HTTP, or user interface.
Q: Are log tables in the database? Do they get cleaned up?
A: Yes there are log tables in the database. By default they are cleaned up every 30 days. We usually recommend the following clean up commands be run weekly:
"C:\Program Files (x86)\Jitterbit Integration Server\bin\JitterbitUtils.exe" --reindex-db
"C:\Program Files (x86)\Jitterbit Integration Server\bin\JitterbitUtils.exe" --reclaim-disk-space
Q: What logfiles can I look at?
A: Jitterbit logs
“C:\Program Files (x86)\Jitterbit Integration Server\log”
This is where the Jitterbit back-end processes write logs: ProcessEngine, OperationEngine, Scheduler, CleanupService and our services implemented in Java (running in Tomcat). These logs are available in the Studio Admin console.
“C:\Program Files (x86)\Jitterbit Integration Server\apache\logs”
This is the standard Apache Httpd log. It shows when somebody accessed Jitterbit from the client (login, log polling or whatever). It is also where to look if Jitterbit Apache doesn't start up or something crashed inside of our apache modules.
“C:\Program Files (x86)\Jitterbit Integration Server\DataInterchange\Temp\LOG”
This is logs from the operation (WriteToOperationLog or warnings from function calls (such as DbExecute failing). They are written to the operation log when the operation finishes. If an operation crashes before that you can find any logs that were written from the operation here.
“C:\Program Files (x86)\Jitterbit Integration Server\tomcat\logs”
Logs from Tomcat. Useful for diagnosing problems with Tomcat start-up.
“C:\Program Files (x86)\PostgreSQL\9.0\data\pg_log”
Log directory for PostgreSQL.
Debug logs are written to
“C:\Program Files (x86)\Jitterbit Integration Server\DataInterchange\Temp\Debug”
This is the default location
- (can be modified in jitterbit.conf [TransformationEngine]/WriteLogDir)
Q: Is messaging support (Message Queue) available?
A: Not supported at this time.
Q: What is the process to promote an integration from a development environment, to a test environment and then to production?
A: Depending on the project variables; Jitterbit uses the concept of "Jitterpaks".Migrating a project to a new environment is done from inside the Jitterbit Design Studio by simply selecting the Migrate function.
Q: What mechanisms are available for monitoring execution and sending alerts if there are problems?
A: Email, Web Management Console, database, etc.
Q: Does Jitterbit provide for monitoring integration with existing systems?
A: Yes. Most monitoring tools have the ability to display the Jitterbit logs as needed. Additionally, Jitterbit provides a command line interface for those who don't want to use the Jitterbit GUI.
Q: What are the monitoring options for Jitterbit? I need to monitor availability, utilization, error rate, etc.
A: The user can manually monitor from inside our Web Management Console. This could also be accomplished using a local web service, or you could query stats within the PostgreSQL DB. There is also the option to write to a file or to the customer’s custom database, depending on the specific requirements.
Q: Does Jitterbit provide the capability to monitor system health?
A: Yes. Jitterbit includes a clean-up service that automatically removes unnecessary integration artifacts on a daily basis. Alerts are made available by designing them into the integrations themselves to provide emails as well as monitoring the administration console.
Q: Does Jitterbit provide a monitoring/management UI?
A: Yes. Jitterbit has a robust monitoring/management UI.
Q: Are operations, code and other authored objects stored on premise?
A: Yes, they are stored on premise.
Q: Are real-time triggers available?
A: Yes. Jitterbit integrations can be configured to be invoked via events in numerous ways. Among them are receiving HTTP posts (both REST & WS), and SAP’s I-DOC receive.
Q: Does your product support real time triggers?
Q: Is real-time auditing support and audit log available?
A: All logs are exposed.
Q: Is real-time logging support available?
Q: Does Jitterbit provide real-time monitoring support?
A: Yes. The Web Management Console provides real-time feedback on the state of the Jitterbit Integration Server/Agent(s) (In-Queue, Running, Processed). Additionally, alerts can be configured for virtually any run-time condition.
Q: Is real-time reporting support available?
A: All logs are exposed.
Q: Does Jitterbit provide extensive reporting of the results of an ETL session, including automatic notification of significant failures of the ETL process?
A: Yes, and it is fully customizable.
Q: How do you reset the PosgreSQL and Jitterbit passwords?
A: Resetting the PostgreSQL admin password:
- Navigate to C:\Program Files (x86)\PostgreSQL\9.0\data
- Open the pg_hba.conf file
- Towards the bottom of the file, update the “Method” from “md5” to “trust” on both the IPv4 and IPv6 local connections.
- Save pg_hba.conf file
- Restart the PostgreSQL Windows service
NOTE: If the following error displays, a reboot of the server/system is required.
NOTE: After rebooting if the PostgreSQL fails to start, change the IPv6 back to md5 and try to restart the Windows service again.
In V5.x you can use the following command to reset password:
- "C:\Program Files (x86)\Jitterbit Integration Server\bin\JitterbitUtils.exe"
- --reset-admin-password "NewPass"
In V4.x or below follow these steps:
- Open the pgAdmin III
- Click on the connect button(looks like a power cord plug)
- Assign it any name you want
- Host = 127.0.0.1
- Password = input anything that you want
- Once connected, click on the SQL button
- Run the following SQL against the TransDb:
- UPDATE UsersTab SET Password='d41d8cd98f00b204e9800998ecf8427e' WHERE User_Id = 0
Once the Query is successfully applied:
- Close out of pgAdmin III
- If closed, open the pg_hba.conf file
- Update “Method” on the IPv4 and/or IPv6 back to “md5”.
- Save file.
- Restart the PostgreSQL Windows service.
Open the Jitterbit Studio Client.
- Once Studio is open, launch the Admin Console.
- You should now be able to log into the local Jitterbit server without entering a password. Leave the password blank.
- Click on “User Console”
- Update password for “admin” account
The Admin account password is now reset. The new password will be required to log into the Admin account.
Q: Does Jitterbit provide the capability to roll back to previous versions?
A: Yes. Jitterbit allows a customer to view / re-deploy virtually any prior instance of a Jitterbit integration.
Q: Is there a Jitterbit component that will route traffic between two Jitterbit servers?
A: The traffic will be routed between the 2 systems with our JMS queue.
Q: What is Jitterbit’s capability around scheduling the solution for batch processing? E.g. day-of-week, hourly, every x-minutes, full CRON like capability, etc.
A: Fully configurable scheduling capabilities are available in Jitterbit.
Q: How does your product support self-health monitoring and alerting?
A: Jitterbit includes a clean-up service that automatically removes unnecessary integration artifacts on a daily basis. Alerts are made available by designing them into the individual integration to provide emails. The user can also monitor all operations viewing the Web Management Console.
Q: Are there per source or per target server / instance charges?
Q: Are service performance stats available?
A: Yes. Every integration instance that is run captures the run time and number of records processed.
Q: What systems administration skills are required?
A: An understanding of the Jitterbit Web Management Console and the OS that you have installed local agents/servers to, on premise.
Q: How are software and/or database updates transmitted to customers?
A: Updates/Upgrades are available for Harmony 7.x as downloads from the Web Management Console on the Dashboard. Updates/Upgrades for Jitterbit 5.x are available as downloads from www.jitterbit.com/customer.
Q: What are the processes used to maintain and verify up-to-date system and application patches/updates?
A: The customer is made aware of all upgrades/patches via email. It is up to the customer to decide whether or not to take advantage of the upgrade. Typically, an upgrade is available every 6 months. Jitterbit continues support on all releases for up to 2 years after a version of the software has been sunset. Additionally, the customer can visit the Jitterbit website to ensure they are running the latest release.Local agents/servers can be upgraded at customers’ convenience. The Jitterbit cloud updates are posted to trust.jitterbit.com
Q: What are the Edition Upgrade options available?
A: Upgrading from one agent/studio version to another is absolutely free. But here are the various options available to upgrade editions:
Q: Are Version Control and Rollbacks available?
A: Any Jitterbit Integration can be rolled back to a previous version with a few simple clicks of the mouse.
Q: Does your product support version control, versioning of components and jobs?
A: Yes. Most customers use a third party version management system of their choosing. Jitterbit also maintains all versions of Jitterbit integration that have been deployed. This allows for rolling back to prior versions of a particular integration if necessary.
Q: Workflow from Development => Test => UAT => Production
A: A customer’s Jitterbit administrator is responsible for moving projects from development through testing and into production in adherence with the customer’s promotion guidelines.
Q: Are XA-Transaction Rollbacks supported?
A: There is no explicit support for this. All roll-backs are designed by the developer in Jitterbit.
Q: Put the question here. Reformat as question if necessary.
A: Put the answer here in italics.
- No labels