Search Engine: Elastic

Article ID: 129551, created on Oct 2, 2016, last review on Apr 18, 2017

Table of Contents

Introduction

This article contains customizations which must be used during the deployment or upgrade of the Azure CSP 3.2+ application.

Preconditions

Before installing or updating the OA Billing customizations, mind the following preconditions:

  1. Odin Automation 7.0.x-7.1.x is installed.
  2. If the O365 application is deployed on your Odin Automation installation, make sure the version of the application is 16.8.3 or higher(16.8.5 or higher in case of Odin Automation 7.1). If Office 365 is 16.8.2, you have to install the unified customization: https://kb.odin.com/en/129444.

Installing OA Billing Customizations

  1. Install the OA Billing control panel customizations:

    1. Log on to the OA Billing Application Server (OABLINFE) as root.
    2. Copy the BM_ProvisioningParams.xml file to the /usr/local/bm/customization.azure directory (create the directory if it does not exist).
    3. Go to the /usr/local/bm/conf/wnd/BM/ directory and create the customization.AZURE symbolic link if the link does not exist. Use the ln -s /usr/local/bm/customization.azure customization.AZURE command.
    4. Copy the script.js file to the /usr/local/bm/conf/html/azure directory (create the directory if it does not exist).
    5. Copy the English localization file (mandatory) and localization files of other necessary languages (optional) to the /usr/local/bm/conf/locale directory:

    6. Restart the www service by using the service www restart command.
    7. Restart the pba service by using the service pba restart command.
  2. Install the OA Billing online store customizations:

    1. Add custom layout template to your online store:

      1. Make sure that the corresponding Service Plan contains the aps_defaults_azure parameter. See Creating 'Azure CSP' Service Plan for more details.
      2. Go to Products > Online Store and select the Layout Templates tab.
      3. Click the Add New Layout Template button.
      4. Type azure_provision in the Layout ID field.
      5. Add the content of the azure_provision.tpl file into the Template text area.
      6. Click the Save button.
    2. Prepare the pemgate layout template:

      1. Go to Products > Online Store and select the Layout Templates tab.
      2. Make sure the pemgate layout template is in the list of layout templates. If it is not in the list, add it by clicking the Add Standard Layout button.
      3. In the list of layout templates, click on the pemgate layout template.
      4. Click the Edit button.
      5. Find the block with the provision.tpl in the template field:

              {if $state->itemIndex == $state->itemOriginalIndex && !$state->subscreen}
                  {GetCustomTemplate name="./provision.tpl" assign="file" }
                  {include file=$file }
              {/if}
        

        and replace it with:

              {if $state->itemIndex == $state->itemOriginalIndex && !$state->subscreen}
                  {GetCustomTemplate name="./azure_provision.tpl" assign="file" }
                  {include file=$file }
              {/if}
        
      6. Click the Save button.
    3. Add custom styles to your online store:

      1. Go to Products > Online Store and select the Design tab.
      2. Click the Edit button.
      3. Add the content of the azure.css file to the existing content of the Customized CSS field.

        Important: Do not remove or change the existing content of the field.

      4. Click the Save button.
    4. Add the English translations (mandatory) and the translations of other necessary languages (optional) to your online store:

      1. Go to Products > Online Store and select the More tab.
      2. Click the Languages link.
      3. Select the required language by clicking the respective link in the Language ID or Language Name column.
      4. Click the Import Dictionary button and select the required dictionary file:

      5. Select the Overwrite Translations checkbox.
      6. Click the Save button.
    5. Go to Products > Online Store and click the Synchronize Now button.

Upgrading OA Billing Customizations

To upgrade the OA Billing customizations, perform the following actions:

  1. Upgrade the OA Billing control panel customizations:

    1. Remove the old customization using this instruction:

      1. Log on to the OA Billing Application Server (OABLINFE) as root.
      2. Go to the /usr/local/bm/customization directory and remove the BM_ProvisioningParams.xml file (if it exists).
      3. Go to the /usr/local/bm/conf/html/azure directory and remove the script.js file.
      4. Go to the /usr/local/bm/conf/locale directory and remove all the locale.<Language ID>.o365-azure files (if they exist).
    2. Install the new OA Billing control panel customizations using the instructions of the Installing OA Billing Customizations section (see step 1).
    3. If the Office 365 application is installed, install the corresponding new OA Billing control panel customizations using the instructions of the https://kb.odin.com/en/129556 KB article.
  2. Upgrade the OA Billing online store customizations:

    1. Remove the old customization using this instruction:

      1. Go to billing in PCP > Products > Online Store > Design tab.
      2. Click the Edit button.
      3. Remove all the css code related to Azure CSP (if there are no stores installed besides Azure CSP and O365, then remove all css code).
      4. Go to Products > Online Store > Layout Templates.
      5. Remove the resourcegate layout template (if it exists).
      6. Remove the o365_provision layout template (if it exists).
      7. If the provision layout template exists, then click on it and then click the Reset To Default button.
    2. Install the new OA Billing online store customizations using the instructions of the Installing OA Billing Customizations section (see step 2).
    3. If the Office 365 application is installed, install the corresponding new OA Billing online store customizations using the instructions of the https://kb.odin.com/en/129556 KB article.

Email subscription for changes to this article
Save as PDF