Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 5 Next »

Introduction

A Jitterbit Cloud Agent Group consists of a set of Jitterbit Harmony 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 Agent Group.

Two Cloud Agent Groups are available:

  • Production Cloud Agent Group: This group is available with a version of the Jitterbit Harmony Agent that is fully tested and ready for production.

  • Sandbox Cloud Agent Group: This group is always the next version of the Jitterbit Harmony Agent, to which the Production Cloud Agent Group will next be upgraded. (Typically, it is the version of the Private Agent included in the latest Harmony Platform release at time of the Sandbox Cloud Agent Group update.)

The Sandbox Cloud Agent Group is available for testing your projects with a new version of Jitterbit Harmony to ensure that you are ready for the next upgrade of the Production Cloud Agent Group. It is not intended as a test environment for your projects prior to “go-live”—that's what a Harmony environment is for—as projects in the Sandbox Cloud Agent, if they use a new feature introduced in that specific version, cannot be moved to the Production Agent Group until the Production Cloud Agent is upgraded to the same version.

Configuration of Cloud Agent Groups

Cloud Agents are configured using the default settings for a Jitterbit Private Agent with these differences:

  • Windows OS authentication for databases is not allowed

  • Key-based SSH login is not allowed

  • ODBC driver access is not allowed

  • Debug logging is not allowed

  • All temp files are cleaned up very quickly; you cannot rely that they are present after an operation runs

  • By default, local files as sources or targets is disabled and they cannot be used on Cloud Agents

  • A project is limited to 8 running operations per agent at any time

  • The maximum time an operation can run (MaxOperationRuntimeSeconds) is set at 21600 seconds (6 hours)

  • A limited group of Jitterbit plugins are available for use on Cloud Agents.

If this configuration does not meet your project requirements, you should use a Private Agent.

Upgrade Schedule

The approximate schedule for upgrading of the Jitterbit Cloud Agent Groups is:

  • A new version of the Jitterbit Private Agent is released approximately every 30 days.

  • Approximately once each quarter, the Sandbox Cloud Agent Group is updated to the latest available Jitterbit Harmony Agent.

  • Approximately 60 days after the Sandbox Cloud Agent Group is updated to a new version, the Production Cloud Agent Group is updated to that same version, allowing time for testing in the Sandbox of Production projects against the upcoming new version.

  • For both Cloud Agent Groups, we will apply updates for known critical defects as we deem necessary. Though we will give advance notice as possible, there can be circumstances where a fix is of such urgency that advance notice is not possible. In all cases, notices will be posted on our status site at https://trust.jitterbit.com.

Production Cloud Agent Group Notes

Production Cloud Agent Group Update
Scheduled for February 6, 2019 in EMEA and February 8, 2019 in NA

This update is 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 is currently available 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.

The Sandbox Cloud Agent Group was updated to version 9.4.2 on January 7, 2019 in both EMEA and NA to match the upcoming 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
Scheduled for February 21, 2019 in EMEA and February 25, 2019 in NA

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

The Sandbox Cloud Agent Group will then be available for testing your projects with Jitterbit Agent version 9.8 to ensure that you are ready when the Production Cloud Agent Group is upgraded in April 2019.

Enhancements

  • 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

  • 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)

On This Page


Last updated:  Feb 04, 2019


  • No labels