Key Concepts and Vocabulary¶

A short list of words that mean something specific in SLIM. Reading this first makes every other page easier.

Project¶

A Project is the container for a unit of modernization work. Everything in SLIM is scoped to a project: access, execution mode, instructions, generated assets.

A project is not the complete scope of all of your integrations, and a project is not a single integration: usually a project comprises multiple integrations and your organization would have several projects depending on the scope of the modernization activity.

Export¶

An Export is the file produced by the source, legacy, integration platform currently running in your environment. It will usually only contain metadata - data about the configuration of the integration - and not any Personally Identifiable Information or sensitive data, though this may depend on the technology in question.

The metadata describes what these integrations do in the production environment today.

When uploaded, the Export is preserved unchanged as a record of the integration on the date it was created.

Integration¶

An Integration is a modernizable unit inside the export. One integration may become more than one SnapLogic pipeline. Conversely many integrations may be consolidated into a single SnapLogic pipeline if there is duplication of logic.

Stage page¶

Each Stage of the SLIM modernization process has a dedicated page that displays the settings used to perform that stage’s activity. These pages are listed down the left side of the application screen - the Project Sidebar - grouped under Current Project.

Job state¶

A Job state records how far the work on an integration has progressed: through its analysis, then its Functional Representation, then its SnapLogic assets. Each of those can be complete or incomplete, and incomplete is not a failure - it means there is more to do, and the work can be run again from that point.

Job states are shown on the Job Status page in the Project Sidebar. Note that a Job state describes an integration’s progress rather than a Stage’s: the Export Analysis and Platform Deploy Stages report their own outcome on their own Stage page instead.

Project busy¶

A Project Busy dialog appears when someone else is already running a task against the Project you are working in, and so the task you want to start cannot begin yet. It names the task that is running, who started it, and how long ago.

This prevents two users running conflicting instructions against the same data, thereby preserving the integrity of the process and the integration.

You can either wait for the running task to finish, or cancel it - the dialog offers both. If nobody appears to be working on the Project and the message persists, your administrator can clear it.