Harmony Quick Upgrade Guide

Transcription

1 Harmony Quick Upgrade Guide UPGRADE IN FIVE EASY STEPS 1. Register for Harmony 2. Set up Environments 3. Download the new Harmony Studio 4. Upgrade your Integration Server to Local or Cloud Agents 5. Convert your existing Jitterbit projects and Jitterpaks WHATS NEW IN HARMONY Jitterbit Harmony (Version 7) is the latest release in Jitterbit s ten-year history to simplify and accelerate enterprise integration. Harmony includes powerful new features for designing, deploying, and managing integrations for the modern enterprise: Harmony Cloud At the core of Harmony is the Jitterbit cloud repository. The repository includes a store, which holds all the projects, and a store, which tracks the activity history and logs. Harmony Environments All projects deployed to Jitterbit Harmony are deployed to Environments. Environments represent virtual folders to store and organize integration projects. Administrators can create unlimited Environments to organize their many projects such as traditional development, test, and production environments. Projects and operations can be easily migrated across environments and Harmony ensures operations running in one environment cannot interact with another project, operation or data used in a different environment. Harmony Local Agents and Agent Groups The Jitterbit Integration server has been redesigned into a lightweight, independent processing engine called a Jitterbit Local Agent. Local Agents are individual run-time engines that run on an individual server behind your corporate. Local Agents are assigned to an Agent Group, which intelligently clusters and synchronizes all other Local Agents within the Agent Group. An Agent Group allows processes to run concurrently across multiple Local Agents. Each Agent Group is designed to be the synchronized run-time environment for one or more Environments.

2 Harmony Cloud Agent Jitterbit Harmony includes a multi-tenant, auto-scaling agent group called Jitterbit Cloud Agent Group. The Jitterbit Cloud Agent Group enables projects to be run 100% in the cloud without the need to install software or hardware. The most common use case is cloud-to-cloud integration. Harmony Design Studio Jitterbit Harmony includes an enhanced visual design studio for connecting to endpoints, data mapping and transformations, and visual and logical process orchestration. Harmony Web Management Console With Jitterbit Harmony, administrators can monitor and manage integration projects over the Internet using the Jitterbit Web Management Console (WMC). The WMC is a HTML5-based tool which perform administration tasks such as manage the users in your organization, configure security and access controls, manage the environments, configure and manage agent groups and agents. UPGRADING TO HARMONY Register for Harmony To begin your upgrade, first you will need to register for Harmony. You can access the login/registration screen at Jitterbit.com. Simply follow the wizard as it sets up a new Harmony user ID, organization and gives you access to your own Web Management Console (WMC). From the WMC, you can administer, monitor and manage all integration projects over the Internet from any browser or device. The WMC is a HTML5-based tool which performs administration tasks such as manage the users in your organization, configure security and access controls, manage the environments, configure and manage agent groups and agents. Create Your First Environment In order to create integration projects in Harmony you will need to create at least one environment. Go to the top menu screen and click on environments. Click on Create

3 Environment button and give your new Environment a name. You can create as many environments as you need. Add Environment Window in Environments Screen Upgrade to the Harmony Studio The new Harmony Studio is required for designing integrations in Harmony. It is available for download from the Web Management Console. The Harmony Studio cannot be configured to connect to your existing Jitterbit Integration Server and previous versions of the Jitterbit Studio will not work with the Harmony platform. Download the new Harmony Studio

4 Create a new project in Jitterbit Studio Upgrade your Jitterbit integration Server to Harmony Agents Upgrading to Local Agents Existing Jitterbit Integration Servers cannot be upgraded or converted into Harmony Local Agents. A Jitterbit Harmony Local Agent is a separate installation. Local Agents are available for download from the Agents Group page in the WMC. Local Agents cannot be installed on the same physical or virtual machine where the Jitterbit Integration Server is installed. Jitterbit Local Agents includes a PostgreSQL database that is installed by default. You also have the option to install the Local Agent database into an existing PostgreSQL database. You should not however, install the Jitterbit Harmony Agent database into an existing Integration Server database. Download a new Local Agent from the Agents Screen

5 Upgrading to Cloud Agents Cloud-to-Cloud integrations can now be run on the new Jitterbit Cloud Agent Group. To run projects in the Cloud, simply select the Jitterbit Cloud Agent Group as the agent group servicing your environment. By doing this, all operations deployed in the environment will be run on the Jitterbit Cloud Agent Group. Associating Cloud Agent Group to your environment You cannot use the Cloud Agent to run your projects if you use any of the following: Source or target as Local File or File Share Re-using the Postgres database bundled with the Integration Server Have custom Plugins installed on the Integration Server Have Hosted Web Services in any of the projects Note: The following are the only standard Plug-ins available on the Jitterbit Cloud Agent Group. If you need to use some of the other standard Plug-ins, you must use a Local Agent. Prepend Data OASIS Web Service Security Jitterbit PGP Encryption Jitterbit PGP Decrypt Private Cloud Agents You can install Local Agents on Private Cloud Services such as Amazon Web Services. Note however, that Jitterbit Harmony agents cannot be installed on the same physical machine or virtual machine where Integration server is installed. Upgrading and deploying existing projects to Jitterbit Harmony. Converting Older Projects and Jitterpaks

6 Converting Projects The new Jitterbit Harmony Studio automatically converts older Jitterbit projects into a format required for Jitterbit Harmony. This conversion is done when an older project is opened in the new Jitterbit Harmony Studio. With Harmony, all projects are deployed to an Environment. To deploy a converted project to an environment, simply select the environment to which the project needs to be deployed. You must create an environment before older projects can be converted. Importing Jitterpaks The new Harmony Studio supports the ability to import Jitterpaks created from older versions of Jitterbit. Choose the Import Jitterpak option when the Harmony Studio is launched. You must create an environment before a project in a Jitterpak can be converted and deployed.

7 * In the first version of Harmony, you will not be able to upgrade projects or import Jitterpaks which use: a LDAP Source / target or the MS CRM or Oracle EBS connectors. Considerations when using the PGP Plug-in The PGP plug-in has been re-designed with Harmony. With 5.3 or older versions of Jitterbit, the PGP plug-in requires the keys to be stored as files on the local disk (on the Integration Server). The path to the key file is then passed as input to the plug-in. With Harmony, the PGP plug-in has been redesigned to take the key directly as input. As a result, you may have to modify the project accordingly. One option is to put the key file on a separate location accessible in a secure manner such as Secure FTP or HTTPS, configure a corresponding Jitterbit Source in the project, and call the ReadFile function to get the key at pass it to the plug-in. Features not available with the current release of Jitterbit Harmony Hosted web services and hosted end-points support on Jitterbit Cloud Agent Group. However, it is available on local agents. Source / target using LDAP Projects connecting MS CRM