When you are migrating from a Full Managed Service to iPaaS, there will be some service components that you did not work with before.
In general, the following service components will be enabled for you:
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:
If you have been using a dedicated BIS system before, there are two options for migrating to iPaaS:
Continuing to use the BIS system of your Full Managed Service
Setting up a new, separate BIS system and migrating step by step
We strongly recommend to set up a new system and not to choose the Big Bang option. With a new system, there will first be a migration from the old BIS system to the staging environment of the iPaaS system, then testing there. When everything runs smoothly, the next step will be moving to production system, switching off the old BIS system and starting on the iPaaS production system. With this method, you can make sure all trading partners are moved successfully and your system is working all the time.
If you choose to continue using the BIS system, it is important to make sure that your existing VPN tunnel will be extended to the new network segment of the iPaaS connection. It also means that all components will be switched to the new network at once (Big Bang). You will therefore take over full responsibility for the processes in your iPaaS system, including process monitoring and troubleshooting with your trading partners if anything is not working properly at the moment of migration.
> 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 who are already 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. |
What will change compared to the Full Managed Service:
You wil have full access to the staging and production environments including the mapping repositories.
You will be responsible for the resolution of processing errors. You will be informed by the SEEBURGER monitoring when a process error occurs.
Your users need to acquire up to date and role-based knowledge on working with the BIS.
You need to agree on a communication matrix (RACI matrix) and on an operations handbook with SEEBURGER.
You need to acquire licenses for the BIC/BIS Mapping Designer.
A handover project for the migration from Full Managed Service to iPaaS is needed.
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:
> Concept of staging and production environment
> Licensing for the BIC Mapping Designer
Home