Cisco Cisco Application Extension Platform for SRE

Copy back any application software that you have changed on the service module to the development 
workstation. For example, use the rsync CLI command.

During this copying, try and avoid copying Cisco add-on packages and embedded guest OS components 
into the application software repository—they already exist on the development workstation. Having 
duplicated files unnecessarily increases the storage space taken up by the application, which has a 
negative effect when the application is later deployed on the Cisco application service module.

On the workstation, create a new package for the application software.

Disable access to the Linux shell if it is not required by the user.

Identify required dependencies upon Cisco add-on packages and the postinstall script.

Delete any unwanted temporary files in preparation for the packaging stage.

Run the library dependency checker tool to verify all libraries required by the application are in the 
package. See the 

.

Package the application using the packaging tool with a dependency on any required Cisco add-on 
packages, and (optional) specify the postinstall script.

(Optional) Bundle the application package with add-on package(s).

Install and test the application package or bundle.

Cisco AXP provides a software development kit (SDK) for developers to use in a Linux development 
environment. 

SDK tools/utilities are explained in the following sections: 

To return to the Table of Contents, click 

To install the Cisco AXP SDK, perform the following steps.

The version of Cisco AXP SDK must be the same as the version of Cisco AXP running on the 
application service module.