When you are migrating from an on-premises BIS to iPaaS, your are already familiar with the BIS and most of the other components of the iPaaS service.
In general, the following service components are used:
BIS Front End
BIS and/or BIC Mapping Designer
MapTable Manager
Message Tracking
You can find the complete list of components used in iPaaS here:
When migrating from your on-premises BIS to the staging environment of the iPaaS system, you can transfer some of your configurations to the iPaaS system, i.e. entities, mappings and the basic master data for your ERP system.
Prerequisites for the transfer of configurations:
the same version of the BIS
the same version of the Service Pack
the same version of the BIS/BIC Mapping Designer
the same version of the B2B/MFT Packaged Solution
identical logical system names, both, on-premises and in the Cloud
the connection between your on-premises BIS and the iPaaS BIS requires a VPN tunnel.
A new, separate system will be set up for you. With the new system, there will first be a migration from your on-premises BIS to the staging environment of the iPaaS system, then testing there. When everything runs smoothly, the next step will be moving to production environment, switching off the on-premises BIS and starting on the iPaaS production environment. With this method, you can make sure all trading partners are moved successfully and your system is working all the time.
The concept of a staging and a production environment might be new for you. If you did not use a staging/test environment before, you can still move your configurations via the Move to Production tool from your on-premises production environment to the iPaaS staging environment.
> Concept of staging and production environment
|
Note: Trading partners connected directly via the internet and the BIS might require a change on their side because a parallel system will be set up which they will need to connect to. Informing the trading partners is in your responsibility. Trading partners connected via the SEEBURGER Cloud Gateway are not affected but the internal connection between the BIS and the Gateway needs to be switched at once (Big Bang). In this case, SEEBURGER will test the connections to the trading partners beforehand. |
The following questions need to be discussed before the migration:
Which communication protocols are used?
How is the current backend connection set up?
Is the B2B/MFT Packaged Solution already in use? Is a different solution in use?
Is Message Tracking already in use?
Which mappings are used?
How should archiving be set up?
SEEBURGER does not offer archiving options but provides the data which has been processed within iPaaS for your archiving system.
The migration project is basically carried out like an initial project for new customers, only the duration of the project phases may vary depending on your individual situation and requirements:
Find more information here:
Home