Going live

Setting up the customer environment (Lime)

This is preferably done a couple of days before the "going live weekend". This is most often done after work hours, ~17:00. During this setup the standard installation process for this integration is followed, see Installation.

After the installation it is VERY important to validate the functionality of both the BFUS integration and the customers standard Lime workflow. Involve the customer themself if support is needed for the validation of Lime workflow. Validating the integration is most easily done through example xml:s and Postman.
* Postman collection with example requests can be found at, F:\Common\Industry Experts\Utility\Integrations\BFUS 2.0. * Example files are found at, F:\Common\Industry Experts\Utility\Integrations\BFUS 2.0\Exempelfiler.

Object order for initial loading of BFUS data

  1. Productrow
  2. Customer
  3. Utilityservice
  4. Connection
  5. Flexserviceplace
  6. Flexservice
  7. Contract
  8. Notification/Comment

Initiate file migration from Lime server

The .py files needed will be found in the "bfus-template-solution". Files needed are:
- migration.py (root-folder)
- endpoints_migration.py (endpoint-folder)

Before we unpack the .zips from CGI we need to create the folder we will use for the migration, create the following folder structure: "C:\Lime\bfus_temp_xmls".

After CGI have sent Lime the files we will unpack the CGI .zips in the order described in the section above and in the location mentioned above. For one object at the time we will start the migration through an endpoint request from Postman. The Postman collection can be found at, "F:\Common\Industry Experts\Utility\Integrations\BFUS 2.0\BFUS 2.0.postman_collection.json". The request is called "Handle migration queue (files)" in the collection.

The migration script will iterate files from the root folder in "C:\Lime\bfus_temp_xmls" and after a batch of files been handled they will be moved to the sub-folder "processed". The processed-folder is something created by the migration script. The script will create sub-folders in the processed-folder with todays date, the date the migration is initiated, where it will place the handled files.

CGI routine for initial loading of BFUS data to LIME

2 weeks before going live:

  • CGI checks for data that may need to be corrected for the integration service in BFUS to work. This is sent out to the customer for correction (which is done during the week in consultation with CGI).
  • CGI performes communication checks on both the file API and the "regular" API.
  • CGI informs Lime what utilities and telephone number types are in the installation

1 week before going live:

On occasion (for example late afternoon so as not to disturb regular production): - CGI stops the integration service in BFUS - CGI configures a re-direct queue - CGI makes all withdrawals on list file (from customer, utility service, contract, etc.) - CGI starts the integration service

All regular messages from now on are buffered in the "redirect" queue

  • CGI loads its queue and starts integrating messages to the Lime server stored there as files (file api)
  • CGI notifies Lime when this is done (takes a couple of days depending on the amount of data)

Going live weekend:

  • Lime starts loading XML files
  • CGI are available as a stand-by for any problems
  • Lime notifies CGI when file loading is complete
  • CGI stops integration service and transfers the buffered data in the re-direct queue to Lime
  • CGI deleted the re-direct queue. This is most easily done via the "regular" api.
  • CGI starts integration service and checks that there is nothing wrong with regular api transfer The integration is now live and in sync!

NOTE: The possibility of a re-direct queue came in BFUS version 11.9. In the previous version, this can be solved in another way but it requires some manual work.