Skip to content

Limitations - Legacy Services (SAP JCo Connector and Scraper Connector)

After migrating an app that contains legacy services through Visualizer, you can log in to Foundry and view the migrated apps and services.

Limitations for SAP JCo Connector

  • For SAP JCo services, the file name mentioned as value for sapserverfile config-param must be copied to files folder, refer to Folder Structure.

  • When an app that contains an SAP JCo service is migrated, the Service Type field in the integration tab of Foundry Console is filled as SAP JCO Legacy, shown below:

  • In Foundry Console, you can publish SAP JCo services like the other services supported in the ecosystem.

  • You cannot edit SAP JCo services in the Foundry Console. If a user clicks the Edit button for the service, the following app menu appears.

    Note the following supported actions:

    • Edit and Sample code are not supported.
    • Clone, Unlink, Delete, Console Access Control, Export and Import are supported. For details, refer to How to Use Actions on an Existing Integration Service
    • You cannot view operations of an SAP JCo service in Foundry Console.
    • An SAP JCo service is not clickable in the Foundry console. You can only access operations for a SAP JCo service via the service definition XML directly. The Configure Operation button support is not available in the Console.
    • You cannot create SAP JCo services in Foundry Console.
    • For SAP JCo Services, in the integration service designer, the tree view on the left pane when expanded, it will not show any operations even if operations exist within the service definition XML of an SAP JCo service. The operations can only be accessed from within the XML file.

  • While creating an orchestration, object or synchronization service in MobileFoundry 7.x and later, legacy services will not be available for linking.

  • When an app that contains a Synchronization service referenced by legacy services as data source is migrated, sync scopes can only be viewed in Foundry. You cannot edit such sync scopes.

  • When an app that contains an Orchestration service referenced by legacy services is migrated, you can only view operations of the Orchestration service in Foundry. You cannot edit the Orchestration service.

Limitations for Scraper Connector

  • For each scraper service, there should be a corresponding dsl file.

  • If your application is built in Studio versions prior to 6.0, upgrade your project to current version format by using Studio 6.5, and then migrate the app. For more details, refer to Migrate a Project from an Earlier Version of Studio or Iris

  • When an app that contains a Scraper service is migrated, then the Service Type field in the integration tab of Foundry Console is filled as Scraper, shown below:

  • In Foundry Console, you can publish Scraper services like the other services supported in the ecosystem.

  • You cannot edit Scraper services in Foundry Console. If a user clicks the Edit button for the service, the following app menu appears.

    Note the following supported actions:

    • Edit and Sample code are not supported.
    • Clone, Unlink, Delete, Console Access Control, Export and Import are supported. For details, refer to How to Use Actions on an Existing Integration Service
    • You cannot view operations of a Scraper service in Foundry Console.
    • Scraper service is not clickable in the Foundry console. You can only access operations for a Scraper service via the service definition XML directly. The Configure Operation button support is not available in the Console.
    • You cannot create Scraper services in Foundry Console. To create Scraper Services, use older version of Studio 6.5 or below.
    • For Scraper services, in the integration service designer, the tree view on the left pane when expanded, it will not show any operations. The operations can only be accessed from within the XML file.

  • Ensure that DSL files and the corresponding services have the same name otherwise the migration fails.

  • While creating an orchestration, object or synchronization service in MobileFoundry 7.x and later, legacy services will not be available for linking.

  • When an app that contains a Synchronization service referenced by legacy services as data source is migrated, sync scopes can only be viewed in Foundry. You cannot edit such sync scopes.

  • When an app that contains an Orchestration service referenced by legacy services is migrated, you can only view operations of the Orchestration service in Foundry. You cannot edit the Orchestration service.

    Note: Only one property file is allowed.