Article ID: 123239, created on Oct 24, 2014, last review on Apr 21, 2016

  • Applies to:
  • Operations Automation 6.0
  • Business Automation 6.0

Symptoms

After upgrade to OA 6.0 the additional configuration is required. 

Note: This configuration should be performed for upgrades to versions less than 6.0.5; that is, starting from the version 6.0.5, the automated upgrade procedure is done. Except for point 2 - modifying of /etc/httpd/conf.d/ssl.conf.inc on BM host.

Cause

After deployment of Billing as the BSS role, the following APS applications are not updated automatically on the OA Management node:

  • pba
  • csmapi
  • pcpapi
  • templatestore

Requirements

  • OA updated to 6.0 (including Billing module).
  • Application module installed.

Resolution

  1. Perform the following actions to update the applications on the OA Management node:

    1. Download the script attached to this KB article and copy it to OA Management node.
    2. Run the script.
    3. Restart the following services.

      On OA MN:

      service pau stop
      service pem stop
      service pau start
      service pem start

      On Billing server:

      service pba restart
  2. Perform the following actions to update configuration files on the Billing Application host:

    1. Log in to the Billing Application host.
    2. In the file:

      /etc/httpd/conf.d/ssl.conf.inc

      add the following lines into the VirtualHost section:

      #added by connect_to_poa.pl
      ServerAlias BA_IP
      ProxyPass /aps http://OAMN_IP:8080/aps
      

      where BA_IP is frontnet IP address of Billing application server, OAMN_IP is the IP address of Operations Automation Management node host

    3. Restart the httpd service:

      service httpd restart
  3. Perform the following actions to update configuration files on the Online Store host:

    1. Log in to the Online Store host.
    2. Retrieve the Billing IP address from the /usr/local/bm/templatestore/conf/params.inc file (it is set for the $SERVER_HOST parameter).
    3. In the files:

      /etc/httpd/conf.d/ssl.conf

      /etc/httpd/conf.d/swshop.conf

      add the following lines into the VirtualHost section:

      SSLProxyEngine on
       ProxyPass /aps https://PBA_IP:443/aps

      where PBA_IP is the IP address of Billing host received on the 2nd step.

    4. Restart the httpd service:

      service httpd restart
  4. Create the APS Billing resource for the Billing APS application package:

    1. In the OA Provider Control Panel, go to Services > Applications and click the Billing package in the list.
    2. Switch to the Resource Types tab and click Create.
    3. Choose Application Service Reference as the base for resource type.
    4. Name the resource type as APS Billing and click Next.
    5. Choose PBA as the APS type.
    6. Click the Billing application resource's ID.
    7. Check your settings and click Finish when done.
  5. Re-run the failed "Provisioning of PACIResourcePA" task for APS Application Cloud Infrastructure.

Search Words

Service Automation 6.0

-

File does not exist: /usr/local/bm/conf/html/aps

Attachments

caea8340e2d186a540518d08602aa065 e12cea1d47a3125d335d68e6d4e15e07 5356b422f65bdad1c3e9edca5d74a1ae 956c448bddc7e1f3585373687602379f 6f1456866eed87488c0f02b298a741c0 198398b282069eaf2d94a6af87dcb3ff 3627d36199b8ff577605df76e2fa222b bb7e9177fb03488961a3ea554120f328

Email subscription for changes to this article
Save as PDF