Article ID: 129444, created on Sep 15, 2016, last review on Mar 14, 2017

  • Applies to:
  • Odin Business Automation Standard 4.5
  • APS 2.x

This article contains the BM_ProvisioningParams.xml and script.js customization files which must be used during the deployment of the Office 365 16.8.1-16.8.2 and Azure CSP 3.1-3.2 applications. These files must be applied on your OA Billing Application Server to configure the subdomain form.

Note: If you plan to install or upgrade Office 365 to 16.8.3+ and Azure CSP to 3.2.4+, you must follow the separate customization instructions: https://kb.odin.com/en/129556 and https://kb.odin.com/en/129551.

Important:

  • Before applying the customizations, make sure that the version of the application used on your installation belongs to the version stated in the KB article. To view the version of the application, log in to your control panel and go to Services > Applications.
  • These customizations require Odin Automation 7.0.
  • The list of customization files for all versions of the Office 365 and Azure CSP applications is provided in the KB article https://kb.odin.com/en/127372.

To learm more about the subdomain form, see the following sections:

  • Odin Automation Office 365 Integration Provider's Guide >> Syndication Partner Scenario > Configuring Office 365 Subdomain Form for OA Billing Control Panel
  • Odin Automation Office 365 Integration Provider's Guide >> Cloud Solution Provider Scenario > Configuring Office 365 Subdomain Form for OA Billing Control Panel
  • Odin Automation Azure CSP Integration Provider's Guide >> Configuring Billing > Configuring Azure CSP Subdomain Form for OA Billing Control Panel

Localization

This article also contains the localization files for nine languages supported in OA Billing. These localization files can be applied for the subdomain form. To do it, perform the following steps:

  1. Download the appropriate localizaton file(s):

  2. Copy files in the /usr/local/bm/conf/locale directory in the OA Billing Application Server.
  3. Execute the service pba restart command.

717db81efe94e616312b74fb03a5d474 70bf700e0cdb9d7211df2595ef7276ab 624ca542e40215e6f1d39170d8e7ec75 caea8340e2d186a540518d08602aa065 400e18f6ede9f8be5575a475d2d6b0a6 70a5401e8b9354cd1d64d0346f2c4a3e

Email subscription for changes to this article
Save as PDF