Cisco DNCS System Release 2.8.1 3.8.1 4.3.1 User Guide

Before you can set up a service to provide subscribers with a third-party application, first prepare the DNCS to
support the application. This section provides an overview of the tasks required to ensure that the DNCS can
support a third-party application.

Make sure that you have completed the following before you begin this process:



Install and configure any hardware required to support the application, such as servers that supply

content for the third-party application.



Load the engine for the third-party application onto the SARA Server.



Consult with the vendor of the application to tailor these procedures to the unique needs of the

application.



Also make sure that you have the following information:



IP address of the server that provides this service (from the vendor of the equipment)



Super user (su) privileges and passwords (from your system administrator)



Your network map

This section provides an overview of the process for preparing the DNCS to support a third-party application.
Click any link to display step-by-step instructions for the procedures summarized here.  

1.

If necessary, Add a VASP Entry to the DBDS. If the application needs to negotiate resources with

the DNCS, add a VASP entry to the DNCS so the DNCS can communicate with the device that provides
third-party application data. If you determine that you need to add a VASP entry, the method you use to
add the VASP depends on your system's configuration.



determine that the application needs to negotiate resources with the DNCS, add a VASP entry to
the DNCS. A VASP entry ensures that the DNCS can communicate with the device that provides
third-party application data.



need to negotiate resources with each RNCS. If so, add a VASP entry for each RNCS so the
RNCS can communicate with the device that provides the third-party application.

Important: Some third-party applications use more than one device to provide data. When this is the
case, you will need to add additional VASP entries so that you have one VASP entry for each device that
provides data. Consult with your third-party application vendor to help you determine the number of
VASP entries you need to add, if any.

2.

 . Adding names to the DNCS hosts table

allows you to type the device name, which is usually easier to remember, instead of the IP address
every time you need to work with the device through the DNCS. Although this step is not required, you
may find completing it is helpful when adding data carousels.

3.

recommendations can help the vendor of the third-party application decide whether a new data carousel
is required for the application or if the application can use an existing data carousel. The vendor will