Skip to end of metadata
Go to start of metadata

Introduction

A Jitterbit Cloud Agent Group consists of a set of Private Agents maintained and managed by Jitterbit. This option allows you to run all of your integrations in the cloud with a scalable, multi-tenant, fault-tolerant clustered Jitterbit Cloud Agent Group.

Production Cloud Agent Group Notes

Production Cloud Agent Group Update to Version 9.4.2
February 6, 2019 in EMEA and February 8, 2019 in NA

This update was an upgrade of the Production Cloud Agent Group from agent version 9.2 to agent version 9.4.2. This includes all updates up to and including the 9.4.2 release.

The Sandbox Cloud Agent Group was made available on January 7, 2019 in both EMEA and NA for testing your projects with Agent version 9.4.2 to ensure that you are ready for this upgrade of the Production Cloud Agent Group.

Enhancements

  • Added the SQL Server Microsoft JDBC Driver to the Jitterbit Harmony Agent. The SQL Server Microsoft JDBC Driver is now included in the Harmony Agent as an alternative way to connect to SQL Server. This fixes a known Date type bug in the jTDS Driver. (Added in 9.3)

Fixes

  • Fixed an issue with retrieval of the NetSuite custom segments to avoid timeout errors while generating or refreshing the schemas. (Added in 9.4.2)

  • Fixed an issue where you were unable to create an SAP RFC function. SAP Remote Function Call now utilizes the user created functions. (Added in 9.3)

  • Fixed an issue where a field is missing on the actual SAP request, which causes the operation to fail. The Agent transformation engine now generates the required XML tag if the element in the schema has 0 occurrences and contains a fixed attribute. (Added in 9.3)

Sandbox Cloud Agent Group Notes

Sandbox Cloud Agent Group Update to Version 10.4
July 17, 2019 in APAC, July 18, 2019 in EMEA, and July 22, 2019 in NA

This update is an upgrade of the Sandbox Cloud Agent Group from agent version 10.3 to agent version 10.4.

Enhancements

  • NetSuite 2019.1 WSDL is now supported
    Support for NetSuite's 2019.1 WSDL is now available for use with Jitterbit's NetSuite connectors. To use the new WSDL, specify its URL during configuration of a Cloud Studio NetSuite connection or Design Studio NetSuite endpoint. Jitterbit continues to be Built for NetSuite (BFN) certified. (Added in 10.4)

Sandbox Cloud Agent Group Update to Version 10.3
June 26, 2019 in APAC, July 8, 2019 in EMEA, and July 10, 2019 in NA

This update is an upgrade of the Sandbox Cloud Agent Group from agent version 10.1 to agent version 10.3. This includes all updates up to and including the 10.3 release.

Fixes

  • Escaping characters in pipe-delimited schemas now works
    When configuring a pipe-delimited custom schema in Cloud Studio or Design Studio, the option to convert escape sequences now works as expected. Previously, using this option with such a schema would cause the operation to fail. (Added in 10.3)
  • An erroneous error no longer appears when testing a Cloud Studio connection
    When testing a connection's configuration in Cloud Studio using the Test button, you will no longer see an erroneous error message indicating the connector is being downloaded across agents when the connection was actually successful. (Added in 10.3)

Sandbox Cloud Agent Group Update to Version 10.1
May 1, 2019 in APAC, May 2, 2019 in EMEA, and May 6, 2019 in NA

This update was an upgrade of the Sandbox Cloud Agent Group from agent version 10.0 to agent version 10.1.

New Features

  • New Cloud Studio connectors
    New Cloud Studio connectors for Evernote, Google Drive, HubSpot, Magento, and SugarCRM are now available to use with agents version 10.1 or higher. The new connectors can be accessed on the right side of the project designer from the design component palette.

Changes

  • The Cloud Studio Cherwell connector no longer works with 10.0 agents
    A change made to the Cherwell connector in Cloud Studio means it is no longer compatible with 10.0 agents. If using the Cherwell connector, please upgrade to 10.1 agents.

Fixes

  • The SendEmail() function now supports multi-byte characters
    The Jitterbit Script function SendEmail() in Cloud Studio or Design Studio can now be used to send emails containing multi-byte characters.

Sandbox Cloud Agent Group Update to Version 10.0
April 4, 2019 in EMEA and April 8, 2019 in NA

This update was an upgrade of the Sandbox Cloud Agent Group from agent version 9.9.0 to agent version 10.0. This includes all updates up to and including the 10.0 release.

Changes

  • The Sandbox Cloud Agent Group no longer supports creating new projects using ODBC drivers. Use a JDBC driver or a Private Agent instead. For assistance, contact Jitterbit Support. (Effective March 26, 2019)

Fixes

  • Fixed an issue with the SAP Connector driver when it is installed for the first time on a Jitterbit Harmony Linux Agent. (Added in 10.0)

Sandbox Cloud Agent Group Update to Version 9.9
March 14, 2019 in EMEA and March 18, 2019 in NA

This update was an upgrade of the Sandbox Cloud Agent Group from agent version 9.4.2 to agent version 9.9. This included all updates up to and including the 9.9 release.

Enhancements

  • LDAP passwords can be set and updated in Jitterbit Script using the LDAP functions(Added in 9.9)
  • The Java distribution included in the Jitterbit Harmony Windows Agent has been changed from the Oracle JRE to the AdoptOpenJDK JRE. (Added in 9.8)

  • Boolean types are now supported for OData when using SQL Server, MySQL, or PostgreSQL. (Added in 9.7)

  • SAP fields defined as doubles now work correctly when used in OData APIs. (Added in 9.7)

Fixes

  • Fixed an issue with the architecture of the third-party SAP JCo (Java Connector) library included in the Jitterbit Harmony Linux Agent. (Added in 9.9)

  • Fixed an issue with the installation of the AdoptOpenJDK JRE by the Harmony Windows Agent installer that prevented certain plugins from functioning. (Added in 9.9)
  • An issue with the Jitterbit global variable jitterbit.source.preserve_char_whitespace not being honored when transforming from CSV to JSON or from an Oracle Database to XML has been fixed. Setting jitterbit.source.preserve_char_whitespace=true means white space will be preserved and won't be trimmed from the beginning and end of strings in the source.

    The default value for this variable is "false", and white space will be trimmed from the beginning and end of strings in the source. This default value will be used if the variable has not been explicitly set. The default behavior is unchanged from prior releases. (Added in 9.8)

  • Fixed an issue with retrieval of the NetSuite custom segments to avoid timeout errors while generating or refreshing the schemas. (Added in 9.7)

  • Fixed an issue in the JMS Connector with messages that are missing a JMS destination header. (Added in 9.7)

  • Fixed an issue with the parsing of IDoc types. It is now enabled. (Added in 9.6)

  • Resolved timeout issues when using JDBC to retrieve a large number of tables. (Added in 9.5)

  • Fixed an Issue with the input parameter of the CVTDate() script function being set to an empty value. The CVTDate() function now successfully converts each input data value to the appropriate date and does not set any input to an empty value. (Added in 9.5)

Known Issues

These issues apply to all recent Cloud Agent Group versions:

  • SFTP directories sometimes aren't auto-created
    • Summary: When writing to SFTP as a target using Design Studio or Cloud Studio, the auto-creation of directories works inconsistently.
    • Additional Info: Depending on the particular FTP server involved, the directory may not be created.
    • Workaround: Confirm that the directory has been created before production use.

  • SetSalesforceSession function doesn't work
    • Summary: The Jitterbit Script function SetSalesforceSession doesn't work correctly and shouldn't be used in Design Studio or Cloud Studio.
    • Additional Info: If used, the script may or may not generate an error. Even if the script does not generate an error, the function will not work correctly. As the function doesn't work, the built-in session handling of the Salesforce connector will be used.

On This Page

Last updated:  Jul 16, 2019


  • No labels