Next you need to install and configure the bc2adls app in your LS Central SaaS environment.
Install and configure
The first two sections in the bc2adls setup documentation, guide you through the process of installing and configuring the app in bc and what is needed in Azure.
You do not have to create a storage account since you have already done the through the deployment script and save in the name of the account and container in the parameter file.
First you should follow the instructions for configuring the storage account and then the instructions for setup and configuration in BC.
Note: In the BC configuration you are asked to build the app from the code provided in the github repostitory. We have already built and tested an app file that you can download and safely install in BC instead of building your own. Use the instruction below to install the app file in BC.
- In LS Central SaaS open Extension management
- Click Manage from the menu and select Upload Extension
- From Select .app file field navigate to the bc2adls app file in the Base folder (product package)
- Swith on the "By deploying this extension..."
- All other fields can be left as they are.
- Click
Then you should go back to the permissions in the configuration in BC section and finish the app configuration in step 4.
When you have finished the Setup configuration, make sure that the Export Enum as Integer and Add delivered DateTime switches are turned on as that is the way we want it for data used in Analytics.
You can then move on to the section below to import the table and field configuration to use in the export.
Import table and field configuration
We have created two table and field configuration files based on whether you are using LS Central for Hotels or not and you can find them in the product package.
- bc2adls_AllTables.xml
- bc2adls_withoutHotels.xml
If you do not have LS Central for Hotels then you should use the file marked "withoutHotels".
- In Export to Azure data lake Storage page navigate to the Tables section menu.
- Click the Import action and drop the xml file you want into the panel that opens up or browse to find the file in the product package base folder.
- A message appears and you should click Yes to continue importing table and field configuration.
- The tables are then loaded into to the tables list and fields selected lists the number or fields that have been selected for export - in this case we have selected all fields that are available for export.
- The reason why we included all the fields is so that it will be easier for you to add more fields to the data warehouse if needed.
The configuration is now ready for export.
Export schema
Before you export data with the bc2adls app you need to export the schema.
- In Export to Azure data lake Storage page click the "v" (downward arrow) next to the Export option in the top menu.
- Select Schema export
- A message will popup about a request being made to the external service. Allow Always is selected and you can click OK
The export will go through all the tables in a Working on it... message box and show for which table it is currently exporting the schema.
Once the schema export is done the message window disappears and if you check the container in Azure you can see that .cmd.json files have been exported for all the tables configured for export.
Save connection string
While you are in the storage account you should need to copy the storage account connection string to the parameters.txt file. Here are instructions on where to find it in Azure.
- Navigate to the Storage account in Azure portal.
- Under Security + networking section in the menu you find Access keys.
- On that page find key1 section Connection String field.
- Click Show button next to the field and then copy the connection string and past in into the parameters.txt file and save it.
Before you continue to export the data you need to use the schema files you just exported to create the prestaging and staging tables in the Analytics data warehouse. This is done by a script and will be explained in the next step.