Previous topic

Deployment

Next topic

Application Icon Design

Provisioning

It is the time to verify if the application subscribes to various events as designed and logs the event notifications in a file.

../../../../_images/event-step-model.png ../../../../_images/event-step-meta.png ../../../../_images/event-step-provision.png ../../../../_images/event-step-presentation.png ../../../../_images/event-step-deploy.png ../../../../_images/event-step-provisioning-b.png

Continue the demo project from the previous step.

Subscribe Customer

If the platform consists of OSS only, follow typical steps to create a subscription in the provider control panel:

  1. Navigate to Operations > Customers to ensure you have a customer for testing. If there is no such a customer, create one.

  2. Open the customer profile, switch to the Subscriptions tab, and create a subscription from the service template.

If the platform contains both OSS and BSS, open the BSS provider control panel and subscribe a customer to the respective service plan.

Test Application in UX1

Log in to UX1 on behalf of your test customer and do the following to test the new application.

  1. Make sure, the VPS Management tab and Event Notifications sub-tab inside it are available.

  2. Follow the Add Users process in the User Management demo to create a user and a VPS for the user.

  3. On the Event Notifications sub-tab, click Refresh to get the event notification log on the screen. Pay attention to the event subscription ID and the source ID, for example:

    ../../../../_images/event-demo-log.png

  4. On the Servers sub-tab, find the new server. Click on its name to run the editor. Edit some properties, including the offer, and save the new configuration.

  5. On the Event Notifications sub-tab, click Refresh to verify if the event notification log is printed out and it presents the expected event notifications: New offer linked and VPS properties changed. For example:

    [24/Mar/2017:16:17:36 UTC] (onVPSofferLink) 172.16.128.41: New offer Linked: {
    "event": "http://aps-standard.org/core/events/linked",
    "time": "2017-03-24T16:17:24Z",
    "serial": 29,
    "subscription": "204ec074-64b5-497f-8477-c80b13a61730",
    "source": {
        "id": "09dcdba9-9f3b-4aa2-b6dc-36fc39cd343f",
        "type": "http://aps-standard.org/samples/event-mgmt/vps/1.0"
    }
}
[24/Mar/2017:16:17:36 UTC] (onVPSchange) 172.16.128.41: VPS properties changed: {
    "event": "http://aps-standard.org/core/events/changed",
    "time": "2017-03-24T16:17:24Z",
    "serial": 30,
    "subscription": "6cff48a5-f6c6-48fb-834b-6a3bb3bcce1d",
    "source": {
        "id": "09dcdba9-9f3b-4aa2-b6dc-36fc39cd343f",
        "type": "http://aps-standard.org/samples/event-mgmt/vps/1.0"
    }
}

  6. In the user panel, navigate to the list of subscriptions and renew the current subscription for the next subscription period.

  7. Return back to the custom Event Notification screen and click Refresh. The event log must contain a notification about the subscription renewal event.

    ../../../../_images/demo-renew-event-log.png

  8. On the Servers sub-tab, remove a VPS. Then remove a user.

  9. Refresh the Event Notifications screen to verify if the new notifications appear there: VPS removed and User removed.

Conclusion

This completes the APS application development cycle. If you experienced any issues when following the project steps, you can download the sample package and compare it with the demo package you have created.