Before You Begin

Four things to have ready before you create your first project.

An export from the source platform

If you want to understand how SLIM can help you, it is helpful to bring an example Export file from your current integration platform for SLIM to analyze.

If you are using SLIM in a learning-only scenario, synthetic data is fine, but this may not reflect a process pertinent to you and your business users, so may hold limited value.

Note: the Export file should be limited in scope for ease of use and speed of processing. SLIM will let you import an entire enterprise-worth of integrations, but it will take some time to get through the initial analysis (without refining the Export Analysis scope), so a smaller Export file would be better here.

Intake is gated by file type, not by platform: if SLIM can open the archive, it will try to analyze what is inside. The practical question is therefore not whether your platform appears on a list, but whether you can get an export out of it.

These are examples of platforms SLIM has analyzed, offered to show the range rather than to set its limits:

  • Alteryx

  • Apache Nifi

  • Axway

  • eQube

  • IBM InfoSphere DataStage

  • Informatica Intelligent Cloud Services (IICS), Intelligent Data Management Cloud (IDMC), PowerCenter

  • Microsoft BizTalk

  • Microsoft SQL Server Integration Services (SSIS)

  • Mulesoft

  • Talend

  • TIBCO

If your platform is not among them, upload an Export file and see what the analysis makes of it. Absence from this list says nothing about whether SLIM can read your export.

A SnapLogic environment to deploy into

The SnapLogic assets will need to be deployed somewhere, so identify and locate credentials for a sandbox or development SnapLogic organization.

If this environment is integrated with your Git or other code management repository, the generated assets can be added to code control on deployment.

Never deploy into a production environment without progressing the generated SnapLogic assets through your code management and deployment process.

Someone who knows the integrations

Having an Export file from your current environment is enough to get started, but working with a stakeholder who knows the integrations - or how the data they provide is used downstream - is especially helpful to bring context to the integration.

This stakeholder will usually become a vital party in understanding and verifying the analysis SLIM performs, and validating the accuracy and behavior of any subsequent generated assets.

Note: this person may not become a SLIM user, but they may be a consumer of the documents produced by and exported from SLIM.

Confirmation that you have been enabled on SLIM

You should have the following in order to access SLIM:

  1. The login URL for your tenant or specific environment.

  2. A username - usually your email address, but this is situation-specific.

  3. A password - usually received from a SLIM administrator.

  4. Membership of at least one Team. Projects belong to Teams, so until you are in one you cannot create a Project - SLIM will tell you as much on the Projects List page.

If you are the lead point of contact for your organization’s SLIM user group, you should also have confirmation that all users’ IP addresses have been configured for access in the SLIM system, and that your organization’s firewall has been configured to permit HTTPS access to the SLIM login URL.

See also